From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi fixes for 2.6.25-rc2
Date: Sat, 23 Feb 2008 14:56:12 -0600 [thread overview]
Message-ID: <1203800172.3139.7.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.00.0802231229320.21332@woody.linux-foundation.org>
On Sat, 2008-02-23 at 12:31 -0800, Linus Torvalds wrote:
>
> On Sat, 23 Feb 2008, Jeff Garzik wrote:
> >
> > I know I am probably shooting myself in the foot here, since I am the original
> > author of mvsas, but...
> >
> > Should we be adding new drivers during -rc?
>
> I'm personally of the opinion that a new driver that doesn't add anything
> but itself (ie no infrastructure changes etc) is fine. I'd rather have a
> new, rough driver that might work, than no driver at all, and it's not
> like it can cause a regression if you don't enable it.
That is the case for this one. The two patches only touch the mvsas.c
file (and Makefile and Kconfig to build it, of course).
James
next prev parent reply other threads:[~2008-02-23 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 15:13 [GIT PATCH] scsi fixes for 2.6.25-rc2 James Bottomley
2008-02-23 20:25 ` Jeff Garzik
2008-02-23 20:27 ` Jeff Garzik
2008-02-23 20:31 ` Linus Torvalds
2008-02-23 20:44 ` Andrew Morton
2008-02-23 23:53 ` Jeff Garzik
2008-02-23 20:56 ` James Bottomley [this message]
2008-02-25 22:39 ` Martin Michlmayr
2008-02-25 22:54 ` Byron Bradley
2008-02-26 9:28 ` Jean Delvare
2008-02-26 11:15 ` Alessandro Zummo
2008-02-23 23:01 ` Olof Johansson
2008-02-23 23:31 ` Jeff Garzik
2008-02-24 0:09 ` James Bottomley
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=1203800172.3139.7.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.