linux-kernel - Re: [GIT PULL] iBFT features for v2.6.36 .. Question about LinuxCon.

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: <20100804133830.GA4789@phenom.dumpdata.com>
Date:	Wed, 4 Aug 2010 09:38:30 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...nel.org>
To:	torvalds@...ux-foundation.org
Cc:	Peter Jones <pjones@...hat.com>,
	Konrad Rzeszutek Wilk <konrad@...nel.org>,
	Konrad Rzeszutek <konrad@...a.kernel.org>,
	torvalds@...ux-foundation.org, James.Bottomley@...e.de,
	linux-kernel@...r.kernel.org, lenb@...nel.org,
	michaelc@...wisc.edu, mcb30@...e.org
Subject: Re: [GIT PULL] iBFT features for v2.6.36 .. Question about LinuxCon.

On Tue, Aug 03, 2010 at 04:23:19PM -0700, H. Peter Anvin wrote:
> On 08/03/2010 07:35 AM, Peter Jones wrote:
> > 
> > The current iBFT specification and the current code (this push) includes the
> > ability to specify the location of the iBFT table using the standard ACPI table
> > mechanism, which is required on UEFI machines supporting iBFT, and which I
> > would encourage non-UEFI machines to also use where possible.  Obviously some
> > systems, especially BIOS-based machines doing iSCSI boot on expansion cards,
> > have difficulty with this, so we're not planning on de-supporting the old
> > memory scanning method.
> > 
> 
> Not just expansion cards, but also post-INT19 software solutions.

Linus,

Aside the discussion we are having with hpa about expanding the iBFT
or morphing it in another beast I realized that the LinuxCon is right
around the corner.

I presume you are not going to be sitting in the back of a corner trying
to merge all of the GIT pulls right before Aug 14/15th during the
LinuxCon. So does that mean that the effective merge window is right
before LinuxCon?

If that is the case, ping! Please pull this in before you pull in
James's tree as he has patches (and post-post merge patches) that depend
on this tree.

Or by any chance are you expanding the merge window by an extra week?

P.S.
Sorry to be so noise about this, but in the past I had missed two merge
windows and I want to make sure I don't miss this one.
--
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/