linux-kernel - Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Sep 2015 09:33:36 +0100
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Mark Brown <broonie@...nel.org>,
	Nariman Poushin <nariman@...nsource.wolfsonmicro.com>,
	Lee Jones <lee.jones@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH 1/2] mfd: Fixup clients of
 multi_reg_write/register_patch

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@...b.auug.org.au> wrote:
> >
> > On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin <nariman@...nsource.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@...nsource.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/