Re: Firmware patches for SCSI

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Sat, 2008-12-20 at 02:11 +0530, Jaswinder Singh wrote:
> Hello James,
> 
> On Sat, Dec 20, 2008 at 1:59 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > Um ... depends how they got into linux-next.  The head commit just says
> >
> 
> They got into linux-next via David Woodhouse. :
> http://git.infradead.org/users/dwmw2/firmware-2.6.git
> 
> > Merge commit 'firmware/master'
> >
> > Which isn't very descriptive of where it came from.  It looks like
> > either a tree that linux-next shouldn't pull (or one the owner forgot to
> > push to linus).
> >
> 
> Earlier due to Firmware issues firmware patches are going directly
> though David Woodhouse.
> 
> Now firmware issues are solved so David wants that the _driver_
> patches should be sent directly to the appropriate maintainers / mailing lists.

OK, then whatever tree contains them needs to eject them or be dropped
from linux-next.

> So I am curious that should I resend these patches based on which git tree.

Yes please.  For me it would be against scsi-misc ... for the other
drivers it would be their development tree.  The simplest thing to do is
probably to rebase them all on top of linux-next (which contains all of
our trees) and then send them to the individual subsystem maintainer
lists.

James