linux-kernel - Re: [PATCH 0/15] arizona updates for v3.10

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130408092556.GL24058@zurbaran>
Date:	Mon, 8 Apr 2013 11:25:56 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH 0/15] arizona updates for v3.10

Hi Mark,

On Wed, Apr 03, 2013 at 07:04:23PM +0100, Mark Brown wrote:
> On Mon, Apr 01, 2013 at 06:27:48PM +0100, Mark Brown wrote:
> 
> > mfd: arizona: Updates for v3.10
> > 
> > This is really a few separate topics which I can split out if required:
> > 
> >  - WM5102 updates to improve robustness
> >  - Improved support for interoperation with edge triggered interrupt
> >    controllers
> >  - Support for some unusual clocking configurations
> >  - A couple small single patch updates and fixes
> > 
> 
> A few more updates for this which I'll post just now, I've updated the
> tag and branch:
> 
> The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
> 
>   Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git tags/mfd-arizona-3.10
Thanks, I pulled this one into mfd-next now.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/