From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: recalljeffchang@gmail.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH acs_ame scsi driver 000 of 1] Introduction
Date: Tue, 11 Dec 2007 16:24:08 -0800 [thread overview]
Message-ID: <20071211162408.54544ec3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071210165548.GC26334@parisc-linux.org>
On Mon, 10 Dec 2007 09:55:48 -0700
Matthew Wilcox <matthew@wil.cx> wrote:
> On Mon, Dec 10, 2007 at 12:03:18PM +0800, chang jeff wrote:
> > Dear Sir,
> >
> > Following is patche for scsi driver in 2.6.23.9 what should get into
> > 2.6.23.9-final if possible.
> >
> > First refines a newly created scsi driver
> > (/[kernel-version]/driver/scsi/acs_ame).
> >
> > Thanks,
> > JeffChang.
>
> Hi Jeff,
>
> You don't seem to have attached the driver ... maybe you sent a second
> email that hasn't arrived yet? I see Andrew sent a mail (possibly to
> one of your colleagues?) that explains that he doesn't personally take
> scsi driver patches: http://lkml.org/lkml/2007/8/30/7
>
Well, I'll pass an eye over them and will queue them up for a bit or
review-and-test if it looks like they're being neglected.
However I can't queue this one because a) it's wordwrapped and b) there are
patches in -mm which remove scsi_cmnd.request_buffer (and probably other
things).
But that doesn't prevent scsi developers from performing code review.
next prev parent reply other threads:[~2007-12-12 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 4:03 [PATCH acs_ame scsi driver 000 of 1] Introduction chang jeff
2007-12-10 16:55 ` Matthew Wilcox
2007-12-12 0:24 ` Andrew Morton [this message]
2007-12-12 0:45 ` Randy Dunlap
[not found] ` <20071211170148.6c0283f8.akpm@linux-foundation.org>
2007-12-12 1:15 ` Andrew Morton
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=20071211162408.54544ec3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=recalljeffchang@gmail.com \
/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