All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Kyle McMartin <kyle@mcmartin.ca>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Changes to fcntl.h and F_* numbers?
Date: Sun, 29 Nov 2009 20:55:41 +0100	[thread overview]
Message-ID: <4B12D1BD.90602@gmx.de> (raw)
In-Reply-To: <119aab440911291017h1704a159j61421323b8099a3@mail.gmail.com>

On 11/29/2009 07:17 PM, Carlos O'Donell wrote:
> On Fri, Nov 27, 2009 at 5:20 PM, Helge Deller<deller@gmx.de>  wrote:
>> Hi Carlos,
>>
>> FWIW, Stephen's patch has been applied to mainline (2.6.32-rc8) in the
>> meantime...
>
> Thanks Helge. Could you do some sleuthing for me? Were the F_SETOWN_EX
> and F_GETOWN_EX ever in any released kernel?

Those were added by this commit:

commit ba0a6c9f6fceed11c6a99e8326f0477fe383e6b5
Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date:   Wed Sep 23 15:57:03 2009 -0700
     fcntl: add F_[SG]ETOWN_EX

Linux kernel 2.6.31 was tagged:
Date:   Wed Sep 9 15:13:59 2009 -0700
(according to the git-log of the top Makefile)

So I don't think they were ever in any released kernel.

Helge

  reply	other threads:[~2009-11-29 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 20:22 Changes to fcntl.h and F_* numbers? Carlos O'Donell
2009-11-19  3:22 ` Kyle McMartin
2009-11-19 17:00   ` Carlos O'Donell
2009-11-19 17:23     ` James Bottomley
2009-11-20 22:57       ` Carlos O'Donell
2009-11-27 22:20         ` Helge Deller
2009-11-29 18:17           ` Carlos O'Donell
2009-11-29 19:55             ` Helge Deller [this message]
2009-11-30  0:19               ` Carlos O'Donell
2009-11-30  6:18               ` Kyle McMartin

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=4B12D1BD.90602@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=carlos@systemhalted.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@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 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.