From: David Miller <davem@davemloft.net>
To: samuel.thibault@ens-lyon.org
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] no SA_NODEFER on sparc?
Date: Sat, 23 Sep 2006 17:39:24 -0700 (PDT) [thread overview]
Message-ID: <20060923.173924.78710069.davem@davemloft.net> (raw)
In-Reply-To: <20060908000602.GJ8569@bouh.residence.ens-lyon.fr>
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Fri, 8 Sep 2006 02:06:02 +0200
> I noticed that the sparc arch misses a definition for SA_NODEFER. Is
> that on purpose? If not, here is a patch for fixing this.
>
> Add SA_NODEFER, deprecating linuxish SA_NOMASK.
>
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
I have no problems with this patch. Userland headers already
define both SA_NODEFER and SA_NOMASK on Sparc.
next prev parent reply other threads:[~2006-09-24 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 0:06 [PATCH] no SA_NODEFER on sparc? Samuel Thibault
2006-09-08 0:10 ` clean SA_NOMASK usage Samuel Thibault
2006-09-24 0:39 ` David Miller [this message]
2006-09-24 7:59 ` [PATCH] no SA_NODEFER on sparc? Jan Engelhardt
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=20060923.173924.78710069.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=sparclinux@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