From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
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: ksignal changes for 3.9
Date: Wed, 13 Feb 2013 12:06:30 +0530 [thread overview]
Message-ID: <511B346E.2090900@synopsys.com> (raw)
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.
Thx,
-Vineet
next reply other threads:[~2013-02-13 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 6:36 Vineet Gupta [this message]
2013-02-14 23:34 ` ksignal changes for 3.9 Al Viro
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=511B346E.2090900@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.