From: Ulrich Drepper <drepper@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
linux-api@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Oleg Nesterov <onestero@redhat.com>,
Stephane Eranian <eranian@googlemail.com>,
Michael Kerrisk <mtk.manpages@googlemail.com>,
Roland McGrath <roland@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: F_SETOWN_EX and F_GETLK64 conflict
Date: Thu, 29 Oct 2009 20:21:02 -0700 [thread overview]
Message-ID: <a36005b50910292021y392075d5lddc620e3bdfc3ede@mail.gmail.com> (raw)
In-Reply-To: <1254691822.21044.9.camel@laptop>
On Sun, Oct 4, 2009 at 14:30, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> arch/alpha/include/asm/fcntl.h | 4 ++--
> include/asm-generic/fcntl.h | 19 +++++++++++--------
> 2 files changed, 13 insertions(+), 10 deletions(-)
This patch looks fine:
Acked-by: Ulrich Drepper <drepper@redhat.com>
Linus, can you please apply it in whatever form so that we know the
value of the constants?
next prev parent reply other threads:[~2009-10-30 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0910041229300.20203@digraph.polyomino.org.uk>
2009-10-04 21:30 ` F_SETOWN_EX and F_GETLK64 conflict Peter Zijlstra
2009-10-29 17:03 ` Andreas Schwab
2009-10-30 3:21 ` Ulrich Drepper [this message]
2009-10-30 5:13 ` Stephen Rothwell
2009-10-30 5:29 ` Stephen Rothwell
[not found] ` <20091030162906.fbc1c40b.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-12 23:32 ` Stephen Rothwell
[not found] ` <20091113103257.1f4f6e12.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-14 7:01 ` [PATCH] fcntl: use architecture independent values for new fcntl operations Stephen Rothwell
[not found] ` <20091114180131.da95d2a1.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-14 9:45 ` [PATCH v2] fcntl: Use consistent values for F_[GS]ETOWN_EX Stephen Rothwell
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=a36005b50910292021y392075d5lddc620e3bdfc3ede@mail.gmail.com \
--to=drepper@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=eranian@googlemail.com \
--cc=hch@infradead.org \
--cc=joseph@codesourcery.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@googlemail.com \
--cc=onestero@redhat.com \
--cc=roland@redhat.com \
--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 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).