linux-kernel - Re: [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Mar 2011 16:10:10 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Dave Jiang <dave.jiang@...el.com>, linux-scsi@...r.kernel.org,
	jacek.danecki@...el.com, ed.ciechanowski@...el.com,
	linux-kernel@...r.kernel.org, dmilburn@...hat.com,
	edmund.nadolski@...el.com, Jeff Garzik <jeff@...zik.org>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] firmware/efi: export a routine to retrieve efi-variables
 by GUID

On Fri, Mar 18, 2011 at 3:50 PM, Greg KH <gregkh@...e.de> wrote:
>> Not sure who looks after efivars.c, but get_maintainer.pl and git shortlog
>> fingered Greg as a likely target.
>
> Yes, that is me.

Sorry Greg, didn't mean to refer to you in the third person.

>
>> We are currently targeting a late merge of the isci driver through the
>> staging tree into 2.6.39.  This is a pre-requisite to be able to use the
>> driver on an efi enabled platform.
>
> You are?  That's news to me, why didn't you ask the staging tree
> maintainer about this?

This was a very recent, two days ago discussion on linux-scsi [1] with
Jeff and Christoph that you should have been copied on...

> I needed all patches in linux-next _before_ the merge window opened to
> be able to accept it.

Yes, I know, and as dmaengine maintainer I also hate being ambushed by
last minute patches, but now I am unfortunately one of those annoying
people on the other side of the coin.

The review has been intermittent until very recently.  Given that
fact, James was understandably not ready to take it into
drivers/scsi/.  So the thought was to leave time for the review to pan
out and then attempt a post -rc1 merge through scsi or staging.

> So, sorry, it will have to wait until .40.
> Please send me the isci driver and I will be glad to queue it up for
> staging for that kernel.

We will submit a revised driver in the next few weeks.

--
Dan

[1]: http://marc.info/?l=linux-scsi&m=130022318906252&w=2
--
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/