From: Oleg Nesterov <oleg@redhat.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH 0/2] block_sigmask() helper function
Date: Thu, 22 Dec 2011 18:51:23 +0100 [thread overview]
Message-ID: <20111222175123.GA4895@redhat.com> (raw)
In-Reply-To: <1324493221-4435-1-git-send-email-matt@console-pimps.org>
On 12/21, Matt Fleming wrote:
>
> Hi Andrew,
>
> Oleg doesn't have a repo on kernel.org yet and suggested that you
> might take these patches through your -mm tree?
Yes, could you take this please? I have no idea when I will restore
my korg account. If ever :/
> Ideally I'd like to
> get these two in for the 3.3 merge window because I've got a bunch of
> other patches that can go through the respective maintainers' trees
> once these two have been merged.
I was surpised by how many bugs there are in arch/ signal code, this
patch helps to factor out the code in the signal-deliver paths.
Oleg.
prev parent reply other threads:[~2011-12-22 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 18:46 [PATCH 0/2] block_sigmask() helper function Matt Fleming
2011-12-21 18:47 ` [PATCH 1/2] sparc: Make SA_NOMASK a synonym of SA_NODEFER Matt Fleming
2011-12-21 20:31 ` David Miller
2011-12-21 20:31 ` David Miller
2011-12-22 18:02 ` Oleg Nesterov
2011-12-22 18:02 ` Oleg Nesterov
2011-12-21 18:47 ` [PATCH 2/2] signal: Add block_sigmask() for adding sigmask to current->blocked Matt Fleming
2011-12-22 17:52 ` Oleg Nesterov
2011-12-22 17:51 ` Oleg Nesterov [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=20111222175123.GA4895@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.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 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.