From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
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 18:53:14 -0500 [thread overview]
Message-ID: <47C0B1EA.4010400@garzik.org> (raw)
In-Reply-To: <20080223124445.db779e3c.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 23 Feb 2008 12:31:02 -0800 (PST) Linus Torvalds <torvalds@linux-foundation.org> 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.
>>
>
> Yes, I too think that adding new standalone code in late -rc is OK.
ACK, thanks!
Jeff
next prev parent reply other threads:[~2008-02-23 23:53 UTC|newest]
Thread overview: 10+ 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 [this message]
2008-02-23 20:56 ` James Bottomley
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=47C0B1EA.4010400@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox