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 micha...@cs.wisc.edu wrote:
> > > From: Mike Christie <micha...@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 <micha...@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 ***

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to