From: "Jaswinder Singh" <jaswinderlinux@gmail•com>
To: James Bottomley <James.Bottomley@hansenpartnership•com>
Cc: linux-scsi@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
sfr@canb•auug.org.au, linux-next@vger•kernel.org,
David Woodhouse <dwmw2@infradead•org>
Subject: Re: Firmware patches for SCSI
Date: Sat, 20 Dec 2008 02:11:04 +0530 [thread overview]
Message-ID: <3f9a31f40812191241q40dafdb0lfd2f4487f2870e2@mail.gmail.com> (raw)
In-Reply-To: <1229718543.18778.4.camel@localhost.localdomain>
Hello James,
On Sat, Dec 20, 2008 at 1:59 AM, James Bottomley
<James.Bottomley@hansenpartnership•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.
next prev parent reply other threads:[~2008-12-19 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:53 Firmware patches for SCSI Jaswinder Singh
2008-12-19 20:29 ` James Bottomley
2008-12-19 20:41 ` Jaswinder Singh [this message]
2008-12-19 20:53 ` James Bottomley
2008-12-22 6:19 ` Stephen Rothwell
2008-12-22 7:48 ` Boaz Harrosh
2008-12-22 15:01 ` James Bottomley
2008-12-22 15:28 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f9a31f40812191241q40dafdb0lfd2f4487f2870e2@mail.gmail.com \
--to=jaswinderlinux@gmail$(echo .)com \
--cc=James.Bottomley@hansenpartnership$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox