linux-kernel - Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable

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:	Wed, 27 Nov 2013 14:19:18 +0000
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	broonie@...nel.org, sameo@...ux.intel.com,
	patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark
	as readable

On Wed, Nov 27, 2013 at 01:24:42PM +0000, Lee Jones wrote:
> > The registers associated with the new channels on AIF2 were accidentally
> > missing defaults and not marked as readable this patch fixes this.
> > 
> > Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
> > ---
> > 
> > This patch depends on the patch:
> > 
> > "ASoC: wm5110: Add extra AIF2 channels"
> > 
> > Which is going through the ASoC tree at the moment, so
> > probably best to send this patch through the ASoC tree as
> > well. As such I have generated it against Mark's for-next
> > branch, let me know if it needs regenerating.
> 
> Hmm... this is awkward!
> 
> I'm not keen on this patch going through ASoC, as it might make things
> equally as awkward later in the cycle. We should have created an
> immutable branch for that really. I guess this will have to wait for
> the next cycle now...

To be honest there is no urgent rush to get this in so it can
wait until the next cycle, I will just have to make sure I
remember to resend.

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/