On Fri, Jul 17, 2015 at 04:29:55PM +0100, Nariman Poushin wrote:
> On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
> > On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
> >
> > > What is the best course of action here? I am more than happy to help with
> > > whatever is
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
> On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
>
> > What is the best course of action here? I am more than happy to help with
> > whatever is needed but unsure of the etiquette here and also not sure
> > what I can
On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
> What is the best course of action here? I am more than happy to help with
> whatever is needed but unsure of the etiquette here and also not sure
> what I can do.
> Clearly there are some clients that need updating but they were
On Fri, Jul 17, 2015 at 02:39:34PM +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> After merging the regmap tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings:
>
> sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
> sound/soc/codecs/wm5110.c:294:9:
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
What is the best course of action here? I am more than happy to help with
whatever is needed but unsure of the etiquette here and also not sure
what I can do.
On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
What is the best course of action here? I am more than happy to help with
whatever is needed but unsure of the etiquette here and also not sure
what I can do.
Clearly there are some clients that need updating but they were not
On Fri, Jul 17, 2015 at 02:39:34PM +1000, Stephen Rothwell wrote:
Hi Mark,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
sound/soc/codecs/wm5110.c:294:9: warning:
On Fri, Jul 17, 2015 at 04:29:55PM +0100, Nariman Poushin wrote:
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
What is the best course of action here? I am more than happy to help with
whatever is needed but
Hi Mark,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
sound/soc/codecs/wm5110.c:294:9: warning: passing argument 2 of
'regmap_multi_reg_write' from incompatible pointer type
Hi Mark,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
sound/soc/codecs/wm5110.c:294:9: warning: passing argument 2 of
'regmap_multi_reg_write' from incompatible pointer type
On Wed, 27 Mar 2013 10:24:57 + Mark Brown
wrote:
>
> On Wed, Mar 27, 2013 at 03:47:37PM +1100, Stephen Rothwell wrote:
>
> > Introduced by commit 45c6a3e449ea ("regmap: cache: Provide a get address
> > of value operation").
>
> Don't know when you grabbed the tree but that's not what's
On Wed, Mar 27, 2013 at 03:47:37PM +1100, Stephen Rothwell wrote:
> Introduced by commit 45c6a3e449ea ("regmap: cache: Provide a get address
> of value operation").
Don't know when you grabbed the tree but that's not what's there now.
signature.asc
Description: Digital signature
On Wed, Mar 27, 2013 at 03:47:37PM +1100, Stephen Rothwell wrote:
Introduced by commit 45c6a3e449ea (regmap: cache: Provide a get address
of value operation).
Don't know when you grabbed the tree but that's not what's there now.
signature.asc
Description: Digital signature
On Wed, 27 Mar 2013 10:24:57 + Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
On Wed, Mar 27, 2013 at 03:47:37PM +1100, Stephen Rothwell wrote:
Introduced by commit 45c6a3e449ea (regmap: cache: Provide a get address
of value operation).
Don't know when you grabbed the tree
Hi Mark,
After merging the regmap tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from drivers/base/regmap/regmap.c:24:0:
drivers/base/regmap/internal.h: In function 'regcache_get_val_addr':
drivers/base/regmap/internal.h:196:2: warning: return
Hi Mark,
After merging the regmap tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from drivers/base/regmap/regmap.c:24:0:
drivers/base/regmap/internal.h: In function 'regcache_get_val_addr':
drivers/base/regmap/internal.h:196:2: warning: return
16 matches
Mail list logo
