linux-kernel - Re: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s

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: <20130517075140.GA25077@balto.lan>
Date:	Fri, 17 May 2013 09:51:40 +0200
From:	Fabio Baltieri <fabio.baltieri@...aro.org>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Lee Jones <lee.jones@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Arnd Bergmann <arnd@...aro.org>,
	Linus Walleij <linus.walleij@...aro.org>, arnd@...db.de,
	Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s

Hello Samuel,

On Fri, May 17, 2013 at 12:43:37AM +0200, Samuel Ortiz wrote:
> > Fabio Baltieri (5):
> >       mfd: abx500-core: Fix sparse warning
> >       mfd: ab8500-sysctrl: Fix sparse warning
> >       mfd: ab8500-sysctrl: Set sysctrl_dev during probe
> >       mfd: ab8500-sysctrl: Let sysctrl driver work without pdata
> Unless I'm missing something here, this one is not really rcN material, so
> I'd appreciate if you could queue it to your for-mfd branch instead.

The last two:

  mfd: ab8500-sysctrl: Set sysctrl_dev during probe
  mfd: ab8500-sysctrl: Let sysctrl driver work without pdata

are actually fixes for bugs introduced in this merge window that
inhibited the ab8500-sysctl driver as a consequence.  Would you
reconsider pulling just those?

Thanks,
Fabio

-- 
Fabio Baltieri
--
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/