linux-kernel - Re: linux-next: manual merge of the scsi tree with Linus' tree

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: <CA+55aFxiichhzqokzAmHMEEUW1286V0d37YaStcOH_e=OutDiA@mail.gmail.com>
Date:	Fri, 20 Jul 2012 09:31:39 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Bottomley <James.Bottomley@...senpartnership.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the scsi tree with Linus' tree

On Fri, Jul 20, 2012 at 12:29 AM, James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
>
> By the way, Linus, the patch says:
>
>     Cc: Dan Williams <dan.j.williams@...il.com>
>     Cc: Alan Stern <stern@...land.harvard.edu>
>     Cc: James Bottomley <jbottomley@...allels.com>
>     Cc: Borislav Petkov <bp@...64.org>
>     Cc: linux-scsi <linux-scsi@...r.kernel.org>
>
> But best I can tell it never went to either me or linux-scsi.

Both you and linux-scsi were cc'd at least in some of the discussion. Search for

  "a7a20d103994fd760766e6c9d494daa569cbfe06 makes kernel 3.5
unbootable on an Intel chipset based motherboard"

but most of the noise is in the bugzilla itself:

  https://bugzilla.kernel.org/show_bug.cgi?id=44771

and it may well be that you weren't listed for the bugzilla entry.

Ugh, how I hate bugzilla.

                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/