linux-kernel - Re: Firmware patches for SCSI

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:	Sat, 20 Dec 2008 02:11:04 +0530
From:	"Jaswinder Singh" <jaswinderlinux@...il.com>
To:	"James Bottomley" <James.Bottomley@...senpartnership.com>
Cc:	linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	sfr@...b.auug.org.au, linux-next@...r.kernel.org,
	"David Woodhouse" <dwmw2@...radead.org>
Subject: Re: Firmware patches for SCSI

Hello James,

On Sat, Dec 20, 2008 at 1:59 AM, James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
>
> Um ... depends how they got into linux-next.  The head commit just says
>

They got into linux-next via David Woodhouse. :
http://git.infradead.org/users/dwmw2/firmware-2.6.git

> Merge commit 'firmware/master'
>
> Which isn't very descriptive of where it came from.  It looks like
> either a tree that linux-next shouldn't pull (or one the owner forgot to
> push to linus).
>

Earlier due to Firmware issues firmware patches are going directly
though David Woodhouse.

Now firmware issues are solved so David wants that the _driver_
patches should be sent directly to the appropriate maintainers / mailing lists.

So I am curious that should I resend these patches based on which git tree.

Thank you,

Jaswinder Singh.
--
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/