Re: [PATCH 2.6.13 1/20] aic94xx: Makefile

2005-09-09 Thread viro
On Sat, Sep 10, 2005 at 12:18:34AM +0400, Alexey Dobriyan wrote: > On Fri, Sep 09, 2005 at 03:32:05PM -0400, Luben Tuikov wrote: > > --- linux-2.6.13-orig/drivers/scsi/aic94xx/Makefile > > +++ linux-2.6.13/drivers/scsi/aic94xx/Makefile > > > +CHECK = sparse -Wbitwise > > make C=1 CHECK="spa

Re: [PATCH 2.6.13 1/20] aic94xx: Makefile

2005-09-09 Thread Luben Tuikov
On 09/09/05 16:18, Alexey Dobriyan wrote: > On Fri, Sep 09, 2005 at 03:32:05PM -0400, Luben Tuikov wrote: > >>--- linux-2.6.13-orig/drivers/scsi/aic94xx/Makefile >>+++ linux-2.6.13/drivers/scsi/aic94xx/Makefile > > >>+CHECK = sparse -Wbitwise > > > make C=1 CHECK="sparse -Wbitwise" > or

Re: [PATCH 2.6.13 1/20] aic94xx: Makefile

2005-09-09 Thread Jeff Garzik
On Fri, Sep 09, 2005 at 03:35:41PM -0400, Benjamin LaHaise wrote: > A single file per patch is not really a patch split up. Patches should > stand on their own, leaving the tree in a compilable functioning state > during each step. Agreed, though for new drivers, this appears to be one way to g

Re: [PATCH 2.6.13 1/20] aic94xx: Makefile

2005-09-09 Thread Alexey Dobriyan
On Fri, Sep 09, 2005 at 03:32:05PM -0400, Luben Tuikov wrote: > --- linux-2.6.13-orig/drivers/scsi/aic94xx/Makefile > +++ linux-2.6.13/drivers/scsi/aic94xx/Makefile > +CHECK = sparse -Wbitwise make C=1 CHECK="sparse -Wbitwise" or make C=1 > +clean-files += *~ Don't override what

Re: [PATCH 2.6.13 1/20] aic94xx: Makefile

2005-09-09 Thread Benjamin LaHaise
A single file per patch is not really a patch split up. Patches should stand on their own, leaving the tree in a compilable functioning state during each step. -ben - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTE