linux-kernel - Re: ksignal changes for 3.9

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] [day] [month] [year] [list]

Message-ID: <20130214233415.GW4503@ZenIV.linux.org.uk>
Date:	Thu, 14 Feb 2013 23:34:15 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	James Hogan <james.hogan@...tec.com>
Subject: Re: ksignal changes for 3.9

On Wed, Feb 13, 2013 at 12:06:30PM +0530, Vineet Gupta wrote:
> Hi Al,
> 
> linux-next contains ksignal conversion for some of the architectures. Are you
> planning to complete that in 3.9 merge window. The reason I ask is so that the
> newer architectures (arc/metag - for a likely 3.9 merge) can queue the
> corresponding changes via respective trees.

That's hardly urgent; as far as I'm concerned, ksignal conversion is for 
3.10-rc1.  OTOH, these helpers are for 3.9-rc1, so any architecture that
cares to switch is welcome to it; less work for me that way.  Hell, as
far as I'm concerned, any maintainer of an in-tree architecture who's happy
with arch-$ARCHITECTURE is welcome to say so and pull it into their tree
right now.  That'll bring the stem of signal.git in, complete with ksignal
helpers to play with.  That part is in no-rebase mode.  The same goes for
arc and metag, except that you'd need to pull the branchpoint of arch-*
(signal.git#Base) instead...
--
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/