From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jaswinder Singh <jaswinderlinux@gmail.com>
Cc: linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Firmware patches for SCSI
Date: Fri, 19 Dec 2008 15:29:03 -0500 [thread overview]
Message-ID: <1229718543.18778.4.camel@localhost.localdomain> (raw)
In-Reply-To: <3f9a31f40812191153n636888f4i549409453266d58c@mail.gmail.com>
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
next prev parent reply other threads:[~2008-12-19 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:53 Firmware patches for SCSI Jaswinder Singh
2008-12-19 20:29 ` James Bottomley [this message]
2008-12-19 20:41 ` Jaswinder Singh
2008-12-19 20:53 ` James Bottomley
2008-12-22 6:19 ` Stephen Rothwell
2008-12-22 7:48 ` Boaz Harrosh
2008-12-22 15:01 ` James Bottomley
2008-12-22 15:28 ` Stephen Rothwell
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=1229718543.18778.4.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=dwmw2@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).