From: "David S. Miller" <davem@davemloft.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Add sparse "__iomem" infrastructure to check PCI address usage
Date: Sun, 12 Sep 2004 17:50:41 -0700 [thread overview]
Message-ID: <20040912175041.71fb385e.davem@davemloft.net> (raw)
In-Reply-To: <4144E93E.5030404@pobox.com>
On Sun, 12 Sep 2004 20:26:38 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:
> Dumb gcc attribute questions:
>
> 1) what does force do? it doesn't appear to be in gcc 3.3.3 docs.
>
> 2) is "volatile ... __force" redundant?
>
> 3) can we use 'malloc' attribute on kmalloc?
Jeff, this code you quoted is in the sparse ifdef block.
next prev parent reply other threads:[~2004-09-13 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409110726.i8B7QTGn009468@hera.kernel.org>
2004-09-13 0:26 ` Add sparse "__iomem" infrastructure to check PCI address usage Jeff Garzik
2004-09-13 0:50 ` David S. Miller [this message]
2004-09-13 2:31 ` Linus Torvalds
2004-09-13 2:41 ` Jeff Garzik
2004-09-13 3:00 ` Linus Torvalds
2004-09-13 14:22 ` Geert Uytterhoeven
2004-09-13 14:33 ` Linus Torvalds
2004-09-13 18:31 ` Tonnerre
2004-09-13 18:48 ` Linus Torvalds
2004-09-13 18:51 ` viro
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=20040912175041.71fb385e.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.