On Mon, May 14, 2012 at 05:40:53PM -0400, Jason wrote:
> Arnd Bergmann <[email protected]> wrote:
> >I just noticed that you said 'for v3.4', not 'for v3.5'. We're really
> >late in the cycle now, so I would only take serious bug fixes and
> >regressions, everything else would better go into v3.5. Which of
> >these are critical and required for v3.4 (i.e. which ones would you
> >backport if v3.4 was already released)?
>
> Yes, my mistake. I thought what Andrew tested was fixes for v3.4.
>
> The only thing I would push to stable and v3.4 is the mv_cesa fix.
> I'll send an amended pull request in a few hours.
The following changes since commit 36be50515fe2aef61533b516fa2576a2c7fe7664:
Linux 3.4-rc7 (2012-05-12 18:37:47 -0700)
are available in the git repository at:
git://git.infradead.org/users/jcooper/linux.git marvell_fixes_for_v3.4
Alexander Clouter (1):
crypto: mv_cesa requires on CRYPTO_HASH to build
drivers/crypto/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
