[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1229718543.18778.4.camel@localhost.localdomain>
Date: Fri, 19 Dec 2008 15:29:03 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Jaswinder Singh <jaswinderlinux@...il.com>
Cc: linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
sfr@...b.auug.org.au, linux-next@...r.kernel.org,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: Firmware patches for SCSI
On Sat, 2008-12-20 at 01:23 +0530, Jaswinder Singh wrote:
> Hello all,
>
> These SCSI's firmware patches are floating in linux-next from long time :
>
> 1. qla1280: use request_firmware
> http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=7c84df1aec1bbb4e43ac9e2ba65b137042279a8d
> 2. advansys: use request_firmware
> http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=baca2b168d3b7340eac87414c046f7d49de4bf71
> 3. qlogicpti: use request_firmware
> http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=2c68b5b6db13786a425accc8576217b120f885f2
>
> Should I need to resend these patches to merge main-stream.
Um ... depends how they got into linux-next. The head commit just says
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).
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists