linux-kernel - Re: [GIT PULL] at91: fixes for 3.12 #1

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] [day] [month] [year] [list]

Message-ID: <CAOesGMjDXFJy3FRRUuFH2EXdwcELYAweqckZfTLrOqEvDoefAw@mail.gmail.com>
Date:	Wed, 25 Sep 2013 21:11:56 -0700
From:	Olof Johansson <olof@...om.net>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	Arnd Bergmann <arnd@...db.de>, "arm@...nel.org" <arm@...nel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
	Ludovic Desroches <ludovic.desroches@...el.com>
Subject: Re: [GIT PULL] at91: fixes for 3.12 #1

On Tue, Sep 24, 2013 at 6:01 AM, Nicolas Ferre <nicolas.ferre@...el.com> wrote:
> Arnd, Olof, Kevin,
>
> This is the first batch of fixes for AT91.
> I think that the removal of the void flag IRQF_DISABLED can be schedulled in
> this timeframe as we are pretty early in the cycle and that this patch
> shouldn't wait more.

Those patches have been trickling in, and I'm not sure if all
maintainers are picking them up for 3.12.

Anyway, it's still fairly early and it's a tiny patch.

>
> Thanks, best regards,
>
> The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
>
>   Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
>
> are available in the git repository at:
>
>   git://github.com/at91linux/linux-at91.git tags/at91-fixes

Pulled, thanks.

-Olof
--
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/