linux-kernel - Re: linux-next: Tree for June 19

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]

Date:	Mon, 29 Jun 2009 09:14:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Len Brown <lenb@...nel.org>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	sfi-devel@...plefirmware.org, x86@...nel.org
Subject: Re: linux-next: Tree for June 19


* Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> > > Basically, this should be just what you would send to Linus 
> > > (or ask him to fetch).  It is allowed to be rebased if you 
> > > deem it necessary.
> > 
> > The patches are tested on the pre-release platform that makes 
> > use of them.  There have been several internal reviews and 
> > re-writes, but since we just got permission to release the 
> > patches last week, they've not been publically vetted yet.
> > 
> > The content is quite close to what I plan to propose for 
> > upstream, but the format is not.  I'll be re-factoring the 
> > series into "clean history" and senting them to LKML on Sunday 
> > night.
> > 
> > I don't expect much comment on the generic part, but will want 
> > x86 maintainers to buy into the parts that touch their 
> > architecture.
> 
> OK, then I think I need to hear from the x86 maintainers, at 
> least, before we include this.

Yep, feel free, the SFI bits looked good in principle.

	Ingo
--
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/