lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1280780042.2843.628.camel@mulgrave.site>
Date:	Mon, 02 Aug 2010 15:14:02 -0500
From:	James Bottomley <James.Bottomley@...e.de>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
Cc:	Mike Christie <michaelc@...wisc.edu>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jayamohan Kallickal <jayamohank@...verengines.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree
 (scsi-post-merge tree related)

On Mon, 2010-08-02 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
> > >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@...nel.org>
>    for the removal from firmware/ibft, and
>  2). Reviewed-by: Konrad Rzeszutek Wilk <konrad@...nel.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?

I can put this patch into my post merge tree.  I suspect you having a
post-post-merge tree (needed for the build problems) might be a bit
overkill ...

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ