From: Arnd Bergmann <arnd@arndb.de>
To: Robert Love <rml@tech9.net>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.5] include/asm-generic/bitops.h {set,clear}_bit return void
Date: Wed, 16 Apr 2003 00:46:20 +0200 [thread overview]
Message-ID: <200304160046.20778.arnd@arndb.de> (raw)
In-Reply-To: <1050442489.3664.159.camel@localhost>
On Tuesday 15 April 2003 23:34, Robert Love wrote:
> > The point of asm-generic is not to use the files, but to give porters a
> > hint about the functionality. Quoting asm-generic/bitops.h:
> >
> > /* For the benefit of those who are trying to port Linux to another
> > * architecture, here are some C-language equivalents. You should
> > * recode these in the native assembly language, if at all possible.
> > * To guarantee atomicity, these routines call cli() and sti() to
> > * disable interrupts while they operate. (You have to provide inline
> > * routines to cli() and sti().) */
> >
> > Or is this comment wrong, too?
>
> Well, the cli() and sti() part is definitely wrong for 2.5.
>
> It is wrong though to assume that nothing will use these; someone may
> copy them directly (and then they do not work) or someone may #include
> this file.
AFAICS, the meaning of the asm-generic directory has completely changed
during the 2.4/2.5 timeframe. They are now meant to be included from
other header files, with the exception of unaligned.h and bitops.h.
These two files are now worthless for the purpose they were meant for. When
someone wants to start a new architecture, the maintained architectures
are the place to look at. For example, the parisc and ia64 implementations
of bitops.h are both generic enough to be used for a new architecture
and they actually are SMP safe and complete, while the asm-generic
variant has been broken since linux-2.0!
> I like Arnd's suggestion to just remove these functions and all other
> instances of them -- assuming in fact they are never used.
I actually meant removing the asm-generic/bitops.h file, not the functions.
Arnd <><
next prev parent reply other threads:[~2003-04-15 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030415174010$3e7e@gated-at.bofh.it>
2003-04-15 20:04 ` [PATCH] [2.5] include/asm-generic/bitops.h {set,clear}_bit return void Arnd Bergmann
2003-04-15 21:27 ` Carl-Daniel Hailfinger
2003-04-15 21:34 ` Robert Love
2003-04-15 22:46 ` Arnd Bergmann [this message]
2003-04-23 18:04 ` Pavel Machek
2003-04-15 17:36 Carl-Daniel Hailfinger
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=200304160046.20778.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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