public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>
Subject: Re: const from include/asm-i386/byteorder.h
Date: 31 May 2003 19:49:53 +0100	[thread overview]
Message-ID: <1054406992.4837.0.camel@sherbert> (raw)
In-Reply-To: <16088.47088.814881.791196@laputa.namesys.com>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

On Sat, 2003-05-31 at 15:10, Nikita Danilov wrote:
> Hello, 
> 
> include/asm-i386/byteorder.h contains strange __const__'s in function
> definitions that have no effect:
> 
> static __inline__ __const__ __u32 ___arch__swab32(__u32 x)
> static __inline__ __const__ __u16 ___arch__swab16(__u16 x)

shouldn't it be __attribute__((const)) to designate a pure function?

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-05-31 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 14:10 const from include/asm-i386/byteorder.h Nikita Danilov
2003-05-31 18:49 ` Gianni Tedesco [this message]
2003-05-31 18:57   ` William Lee Irwin III
2003-06-02 11:51     ` Nikita Danilov
2003-06-02 12:14       ` William Lee Irwin III
2003-06-02 12:36         ` Nikita Danilov
2003-06-02 12:40           ` William Lee Irwin III
2003-06-02 12:59             ` Nikita Danilov
2003-06-02 13:08               ` William Lee Irwin III
2003-06-02 13:21       ` Gianni Tedesco
2003-06-02 13:37       ` Adrian Bunk
2003-06-02 14:46         ` Nikita Danilov

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=1054406992.4837.0.camel@sherbert \
    --to=gianni@scaramanga.co.uk \
    --cc=Linux-Kernel@Vger.Kernel.ORG \
    --cc=Nikita@Namesys.COM \
    /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