Linux PARISC architecture development
 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: Fri, 27 Nov 2009 23:20:13 +0100	[thread overview]
Message-ID: <4B10509D.3020400@gmx.de> (raw)
In-Reply-To: <119aab440911201457j1727576blde3c62569f927711@mail.gmail.com>

On 11/20/2009 11:57 PM, Carlos O'Donell wrote:
> On Thu, Nov 19, 2009 at 12:23 PM, James Bottomley
> <James.Bottomley@hansenpartnership.com>  wrote:
>> On Thu, 2009-11-19 at 12:00 -0500, Carlos O'Donell wrote:
>>> On Wed, Nov 18, 2009 at 10:22 PM, Kyle McMartin<kyle@mcmartin.ca>  wrote:
>>>> On Wed, Nov 18, 2009 at 03:22:15PM -0500, Carlos O'Donell wrote:
>>>>> Kyle, Helge,
>>>>>
>>>>> I've seen some recent churn regarding the kernel fcntl.h and F_* numbers.
>>>>>
>>>>> If our numbers change please keep me in the loop so I can update the C
>>>>> library side.
>>>>>
>>>>
>>>> ?
>>>
>>> http://marc.info/?l=linux-api&m=125688056905828&w=2
>>
>> But this isn't parisc specific ... it's a bug CodeSourcery reported in
>> the ABI assignment in asm-generic.
>
> Yes, that's correct, the original issue doesn't apply to parisc.
>
> I pull from kyle's tree here:
> git://git.kernel.org/pub/scm/linux/kernel/git/kyle/parisc-2.6.git
>
> In kyle's tree I see:
> "arch/parisc/include/asm/fcntl.h"
> #define F_GETOWN_EX     15
> #define F_SETOWN_EX     16
>
> The original message that Joseph Myers at CodeSourcery posted here:
> http://marc.info/?l=linux-api&m=125466028819859&w=2
>
> Does not apply to us.
>
>> We already look to have this sorted out locally in our fcntl.h ... so
>> we're not going to be changing anything, are we?  Or are you saying
>> (because we could get into trouble in future) that we should adopt the
>> asm generic ones?
>
> I don't think we have to change anything.
>
> It would probably be less maintenance for Kyle in the future if we
> adopted the generic ones for future flags.
>
> The message I referenced here:
> http://marc.info/?l=linux-api&m=125688056905828&w=2
>
> by Stephen Rothwell<sfr@canb.auug.org.au>, has a parisc specific piece here:
>
> ~~~
> diff --git a/arch/parisc/include/asm/fcntl.h b/arch/parisc/include/asm/fcntl.h
> index 5f39d55..1e1c824 100644
> --- a/arch/parisc/include/asm/fcntl.h
> +++ b/arch/parisc/include/asm/fcntl.h
> @@ -28,8 +28,6 @@
>   #define F_SETOWN	12	/*  for sockets. */
>   #define F_SETSIG	13	/*  for sockets. */
>   #define F_GETSIG	14	/*  for sockets. */
> -#define F_GETOWN_EX	15
> -#define F_SETOWN_EX	16
>
>   /* for posix fcntl() and lockf() */
>   #define F_RDLCK		01
> ~~~
>
> I don't know why he wants to remove bits from our fcntl.h.
>
> The intent of my original email was to say "Hi! I'm the libc
> maintainer, I'll fix things if you notice a problem."
>
> I'm pretty sure I'm on linux-api, but I missed this issue.
>
> Cheres,
> Carlos.

Hi Carlos,

FWIW, Stephen's patch has been applied to mainline (2.6.32-rc8) in the meantime...

Helge

  reply	other threads:[~2009-11-27 22:20 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 [this message]
2009-11-29 18:17           ` Carlos O'Donell
2009-11-29 19:55             ` Helge Deller
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=4B10509D.3020400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox