linux-kernel - Re: [GIT PULL] First round of SCSI updates for the 3.4+ merge window

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]

Date:	Mon, 21 May 2012 17:52:31 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Bottomley <James.Bottomley@...senpartnership.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] First round of SCSI updates for the 3.4+ merge window

On Mon, May 21, 2012 at 4:30 AM, James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
> The patch contains the usual assortment of driver updates (be2iscsi,
> bfa, bnx2i, fcoe, hpsa, isci, lpfc, megaraid, mpt2sas, pm8001, sg) plus
> an assortment of other changes and fixes.  Also new is the fact that the
> isci update is delivered as a git merge (with signed tag).

Interesting. For some reason the 'gpg --verify' phase says that your
key has expired. Yet when I look at the key itself, it says it is
valid until 2016. I don't quite know why gpg thinks the thing is
expired when verifying the message.

But everything else looks fine. Somebody with more gpg-fu than me
might be able to clarify what is going on..

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