From: Al Viro <viro@ZenIV.linux.org.uk>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
James Hogan <james.hogan@imgtec.com>
Subject: Re: ksignal changes for 3.9
Date: Thu, 14 Feb 2013 23:34:15 +0000 [thread overview]
Message-ID: <20130214233415.GW4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <511B346E.2090900@synopsys.com>
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...
prev parent reply other threads:[~2013-02-14 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 6:36 ksignal changes for 3.9 Vineet Gupta
2013-02-14 23:34 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130214233415.GW4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Vineet.Gupta1@synopsys.com \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).