From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jaswinder Singh <jaswinderlinux@gmail.com>,
linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Firmware patches for SCSI
Date: Mon, 22 Dec 2008 17:19:04 +1100 [thread overview]
Message-ID: <20081222171904.b588da94.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1229720031.18778.8.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
Hi James,
On Fri, 19 Dec 2008 15:53:51 -0500 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> OK, then whatever tree contains them needs to eject them or be dropped
> from linux-next.
That is a problem for me and David. Do not let it concern you ... :-)
> > So I am curious that should I resend these patches based on which git tree.
>
> Yes please. For me it would be against scsi-misc ... for the other
> drivers it would be their development tree. The simplest thing to do is
> probably to rebase them all on top of linux-next (which contains all of
> our trees) and then send them to the individual subsystem maintainer
> lists.
Please don't do that, please base each one on either Linus' tree or the
appropriate maintainer's subsystem tree as linux-next is a moving
target (for instance, if you had based the scsi ones on next-20081219,
then the scsi tree was not included ...). Basing on Linus' tree should
work in most cases as there are not to many conflicts caused by these
patches (the tg3 one is the worst so basing that off the net tree is
probably worth while).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-22 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:53 Jaswinder Singh
2008-12-19 20:29 ` James Bottomley
2008-12-19 20:41 ` Jaswinder Singh
2008-12-19 20:53 ` James Bottomley
2008-12-22 6:19 ` Stephen Rothwell [this message]
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=20081222171904.b588da94.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dwmw2@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®