Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1227538 > unrolled thread

Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH 1/2] mfd: Fixup clients of  multi_reg_write/register_patch Stephen Rothwell <sfr@canb.auug.org.au> - 2015-09-18 06:00 +0200
    Re: [PATCH 1/2] mfd: Fixup clients of  multi_reg_write/register_patch Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2015-09-18 11:00 +0200
      Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Mark Brown <broonie@kernel.org> - 2015-09-18 12:30 +0200

#1227538 — Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch

Hi all,

On Mon, 20 Jul 2015 11:59:35 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin <nariman@opensource.wolfsonmicro.com> wrote:
> >
> > Introduced by:
> > commit 8019ff6cfc04
> > ("regmap: Use reg_sequence for multi_reg_write / register_patch")
> > 
> > Interacting with:
> > commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> > commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
> > 
> > Signed-off-by: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
> > ---
> >  drivers/mfd/wm5110-tables.c | 2 +-
> >  drivers/mfd/wm8998-tables.c | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> I will apply both these patches as merge fix patches in linux-next
> today.  Thanks.

It looks like that patch has been forgotten as I am still applying it
to the linux-next tree every day ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1227662

On Fri, Sep 18, 2015 at 01:50:15PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 20 Jul 2015 11:59:35 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin <nariman@opensource.wolfsonmicro.com> wrote:
> > >
> > > Introduced by:
> > > commit 8019ff6cfc04
> > > ("regmap: Use reg_sequence for multi_reg_write / register_patch")
> > > 
> > > Interacting with:
> > > commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> > > commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
> > > 
> > > Signed-off-by: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
> > > ---
> > >  drivers/mfd/wm5110-tables.c | 2 +-
> > >  drivers/mfd/wm8998-tables.c | 2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > I will apply both these patches as merge fix patches in linux-next
> > today.  Thanks.
> 
> It looks like that patch has been forgotten as I am still applying it
> to the linux-next tree every day ...

Apologies if I am a little out of my depth here, but are we in
the situation where you are expecting this to go through the MFD
tree and Lee is expecting it to go through your tree?

Assuming this is the case, Lee could you perhaps pull this fix in
fairly soon? As it is causing build warning for some configs, in
Linus's tree at the moment. I am quite happy to resend it on
Nariman's behalf if required (he is on holiday at the moment).

Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1227748 — Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch

[Multipart message — attachments visible in raw view] — view raw

On Fri, Sep 18, 2015 at 09:33:36AM +0100, Charles Keepax wrote:
> On Fri, Sep 18, 2015 at 01:50:15PM +1000, Stephen Rothwell wrote:

> > It looks like that patch has been forgotten as I am still applying it
> > to the linux-next tree every day ...

> Apologies if I am a little out of my depth here, but are we in
> the situation where you are expecting this to go through the MFD
> tree and Lee is expecting it to go through your tree?

No, -next is a merge down of trees that will be sent to Linus rather
than a tree that is sent to Linus itself.

> Assuming this is the case, Lee could you perhaps pull this fix in
> fairly soon? As it is causing build warning for some configs, in
> Linus's tree at the moment. I am quite happy to resend it on
> Nariman's behalf if required (he is on holiday at the moment).

I'd recommend resending to make sure Lee has the patch.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web