linux-kernel - Re: [PATCH 1/8] mfd: lpc_ich: Fix ACPI enable bitmask

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]

Message-ID: <20140319171748.GA3842@roeck-us.net>
Date:	Wed, 19 Mar 2014 10:17:48 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Peter Tyser <ptyser@...-inc.com>, linux-kernel@...r.kernel.org,
	James Ralston <james.d.ralston@...el.com>,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: [PATCH 1/8] mfd: lpc_ich: Fix ACPI enable bitmask

On Fri, Mar 14, 2014 at 10:29:34AM +0000, Lee Jones wrote:
> > >>>>The original bitmask of 0x10 was incorrect and would result in a write
> > >>>>to a reserved read-only bit instead of enabling the ACPI I/O
> > >>>>region.  Update it to the proper value of 0x80.
> > >>>>
> > >>>>Signed-off-by: Peter Tyser <ptyser@...-inc.com>
> > >>>>Tested-by: Rajat Jain <rajatjain@...iper.net>
> > >>>>Cc: Guenter Roeck <linux@...ck-us.net>
> > >>>>Cc: James Ralston <james.d.ralston@...el.com>
> > >>>>Cc: Samuel Ortiz <sameo@...ux.intel.com>
> > >>>>Cc: Lee Jones <lee.jones@...aro.org>
> > >>>
> > >>>Who is going to pick up this series ?
> > >>
> > >>I will, once I've completed the review.
> > >
> > >Okay review complete, phew!
> > >
> > >Guenter, How do you want to play this? Do you want me to create an
> > >immutable branch for you to pull from?
> > >
> > 
> > I'll be happy if I can pull it from -next. Is it going to be there
> > anytime soon ?
> 
> Well I pushed an updated version of the MFD today, so it should appear
> in -next this evening.
> 
Hi Lee,

for some reason I still don't see the patches in linux-next, even though I see
them in your mfd-next branch. Any idea what is happening ? Is it possible
that Stephen picks up a different mfd-next tree ?

Thanks,
Guenter
--
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/