From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jayamohan Kallickal <jayamohank@serverengines.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (scsi-post-merge tree related)
Date: Mon, 2 Aug 2010 15:59:40 -0400 [thread overview]
Message-ID: <20100802195940.GC32503@andromeda.dapyr.net> (raw)
In-Reply-To: <4C5717E6.8010805@cs.wisc.edu>
> >Yikes. Last minute change, eh?
>
> I do not know what you mean. The patches always had iscsi_boot_sysfs in
> the firmware dir. You mean this is a last minute change?
Yes, this rename.
>
> >
> >>interface is generic and should be used on any arch and with anything
> >>(ibft or iscsi driver) that wants to export iscsi boot info. The
> >>attached patch moves iscsi_boot_sysfs to drivers/scsi. It was made over
> >>linux-next. I have only compile tested it.
> >
> >did you compile test it with the x86 native iBFT driver?
>
> Yes.
Excellent. The patch does not look like it has changed at all, so:
1). Signed-off-by: Konrad Rzeszutek Wilk <konrad@kernel.org>
for the removal from firmware/ibft, and
2). Reviewed-by: Konrad Rzeszutek Wilk <konrad@kernel.org> for the
the part that puts in drivers/scsi and will make it now under James'
mainternship.
James,
I've asked Linus to pull my iBFT tree before yours as there was this
dependency. Are you OK putting this patch in your tree, or would you prefer
that I expunge Mike's patch from mine?
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-02 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:44 linux-next: build failure after merge of the final tree (scsi-post-merge tree related) Stephen Rothwell
2010-08-02 16:47 ` Stephen Rothwell
2010-08-02 16:54 ` James Bottomley
2010-08-02 17:46 ` Mike Christie
2010-08-02 18:59 ` Konrad Rzeszutek Wilk
2010-08-02 19:09 ` Mike Christie
2010-08-02 19:59 ` Konrad Rzeszutek Wilk [this message]
2010-08-02 20:14 ` James Bottomley
2010-08-03 0:51 ` Konrad Rzeszutek Wilk
2010-08-05 1:55 ` Stephen Rothwell
2010-08-02 16:59 ` Mike Christie
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=20100802195940.GC32503@andromeda.dapyr.net \
--to=konrad@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jayamohank@serverengines.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=randy.dunlap@oracle.com \
--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