From: Randy Dunlap <randy.dunlap@oracle.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, pjones@redhat.com,
open-iscsi@googlegroups.com
Subject: Re: [PATCH 1/2] RFC: iscsi ibft: separate ibft parsing from sysfs interface
Date: Wed, 11 Aug 2010 09:04:45 -0700 [thread overview]
Message-ID: <20100811090445.8462591f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100811085435.7da9dcff.randy.dunlap@oracle.com>
On Wed, 11 Aug 2010 08:54:35 -0700 Randy Dunlap wrote:
> On Mon, 12 Apr 2010 22:20:29 -0400 Konrad Rzeszutek Wilk wrote:
>
> > On Monday 12 April 2010 14:06:17 michaelc@cs.wisc.edu wrote:
> > > From: Mike Christie <michaelc@cs.wisc.edu>
> > >
> > > Not all iscsi drivers support ibft. For drivers like be2iscsi
> > > that do not but are bootable through a vendor firmware specific
> > > format/process this patch moves the sysfs interface from the ibft code
> > > to a lib module. This then allows userspace tools to search for iscsi boot
> > > info in a common place and in a common format.
> > >
> > > ibft iscsi boot info is exported in the same place as it was
> > > before: /sys/firmware/ibft.
> > >
> > > vendor/fw boot info gets export in /sys/firmware/iscsi_bootX, where X is
> > > the scsi host number of the HBA. Underneath these parent dirs, the
> > > target, ethernet, and initiator dirs are the same as they were before.
> > >
> > > This patch was made over the ibft-2.6 tree's ibft-1.03 branch:
> > > http://git.kernel.org/?p=linux/kernel/git/konrad/ibft-2.6.git;a=shortlog;h=
> > >refs/heads/ibft-1.03
> > >
> > >
> > > Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
> > > ---
> > Looks good to my eyes.
> >
> > Let me run it tomorrow through my regression bucket before I stick on the git
> > tree.
>
> Can we get this patch into linux-next, please?
>
> or if it's there, there are still errors like this that need to be checked.
Sorry, I replied to the (a) wrong email (thread).
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-08-11 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 18:06 [PATCH 1/2] RFC: iscsi ibft: separate ibft parsing from sysfs interface michaelc
2010-04-12 18:06 ` [PATCH 2/2] RFC: iscsi ibft: convert iscsi_ibft module to iscsi boot lib michaelc
2010-04-13 2:21 ` Konrad Rzeszutek Wilk
2010-04-13 2:32 ` Mike Christie
2010-04-13 2:36 ` Konrad Rzeszutek Wilk
2010-04-13 14:59 ` Peter Jones
2010-04-13 2:20 ` [PATCH 1/2] RFC: iscsi ibft: separate ibft parsing from sysfs interface Konrad Rzeszutek Wilk
2010-08-11 15:54 ` Randy Dunlap
2010-08-11 16:04 ` Randy Dunlap [this message]
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=20100811090445.8462591f.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=open-iscsi@googlegroups.com \
--cc=pjones@redhat.com \
/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).