[PATCH acs_ame scsi driver 000 of 1] Introduction

[PATCH acs_ame scsi driver 000 of 1] Introduction

[chang jeff]

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.

Re: [PATCH acs_ame scsi driver 000 of 1] Introduction

[Matthew Wilcox]

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

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

Re: [PATCH acs_ame scsi driver 000 of 1] Introduction

[Andrew Morton]

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.

Re: [PATCH acs_ame scsi driver 000 of 1] Introduction

[Randy Dunlap]

On Tue, 11 Dec 2007 16:24:08 -0800 Andrew Morton wrote:

> 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.

but .. but .. where is the patch?
It was missing from the first mail in this thread.

---
~Randy

Re: [PATCH acs_ame scsi driver 000 of 1] Introduction

[Andrew Morton]

On Tue, 11 Dec 2007 17:01:48 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> More hm.  It was from "recalljeffchang@gmail.com" which perhaps means that
> some attempt to recall it was made.  Oh well.

argh.  recalljeffchang@gmail.com really is our Jeff's email address.  And I
went and cc'ed jeffchang@gmail.com on my reply, only that person is an
innocent civilian.  Bad me.  Please remove jeffchang@gmail.com from any
replies.  Thanks.