mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Consolidate include/asm/fcntl.h into include/linux/fcntl.h
Date: Sun, 25 Aug 2002 19:57:45 +1000	[thread overview]
Message-ID: <20020825195745.63ba6fb4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20020824213549.H29958@parcelfarce.linux.theplanet.co.uk>

Hi Willy,

On Sat, 24 Aug 2002 21:35:49 +0100 Matthew Wilcox <willy@debian.org> wrote:
>
> I think this is a bad idea -- when doing a new port, it's easier to fill
> in the bits with the current scheme rather than with your proposed scheme.

The point about nay new port is that it is likely to be exactly the same as
one of the current ports as far as these defines and structures are
concerned.  WIth the current scheme, you get exactly what happened with
PPC and PPC64 - i.e. they are identical with most of the other ports except
for a couple of defines which are only different because of an error.
There is no existing ABI that would be an excuse for them to be different.

With the new scheme, asm/fcntl.h consists of only the necessary
differences from the "norm" as defined by linux/fcntl.h.

Unjustified differences between the ports are a bad thing.  For one,
it make the library maintainers job much harder ...

The longer term intent of my consolidation efforts is to lessen the
problems of all the port maintainers trying to keep up with each other
when bugs are fixed in (more or less generic) code in one port (usually
i386 ...).  There are several bugs like this currently and I suspect
many that have not been discovered yet.

> There is one part which I like:
> 
> -/* for old implementation of bsd flock () */
> -#define F_EXLCK		4	/* or 3 */
> -#define F_SHLCK		8	/* or 4 */
> 
> All of these can go, nobody's been using them since kernel 2.0.  I took
> out the last vestiges of them from locks.c earlier in 2.5.  None of the
> BSDs have them either.

Wonderful, I will update my patch to remove them completely.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

  reply	other threads:[~2002-08-25  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-24 20:35 Matthew Wilcox
2002-08-25  9:57 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-24 15:10 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=20020825195745.63ba6fb4.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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

all inboxes | Powered by JetHome®