From: Jeff Garzik <jeff@garzik.org>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Patch] Shut up warnings from files under drivers/
Date: Sat, 26 Jan 2008 06:44:48 -0500 [thread overview]
Message-ID: <479B1D30.20501@garzik.org> (raw)
In-Reply-To: <20080126101835.GD20935@hacking>
WANG Cong wrote:
> For example, the defination of __devexit_p:
>
> #if defined(MODULE) || defined(CONFIG_HOTPLUG)
> #define __devexit_p(x) x
> #else
> #define __devexit_p(x) NULL
> #endif
>
> If !(defined(MODULE) || defined(CONFIG_HOTPLUG)), __devexit_p
> is just a NULL pointer, thus 'x' may be unused although defined.
...and that's the purpose of the __devexit marker on the code itself.
Jeff
next prev parent reply other threads:[~2008-01-26 11:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 9:30 [Patch] Shut up warnings from files under drivers/ WANG Cong
2008-01-26 9:55 ` Jeff Garzik
2008-01-26 10:18 ` WANG Cong
2008-01-26 11:44 ` Jeff Garzik [this message]
2008-01-26 19:17 ` Sam Ravnborg
2008-01-26 19:30 ` Sam Ravnborg
2008-01-27 2:50 ` WANG Cong
2008-01-27 4:15 ` (Updated) " WANG Cong
2008-01-27 9:08 ` Jiri Slaby
2008-01-27 9:21 ` Jiri Slaby
2008-01-28 5:20 ` WANG Cong
2008-01-27 9:21 ` Sam Ravnborg
2008-01-28 5:49 ` (Try#3) " WANG Cong
[not found] ` <1201691351-1038?= =?ISO-8859-1?Q?4-1-git-send-ema?= =?ISO-8859-1?Q?il-=1B[D>
2008-01-30 11:10 ` [PATCH 1/2] Char: applicom, use pci_resource_start Jiri Slaby
2008-01-30 11:13 ` Jiri Slaby
2008-01-30 11:13 ` [PATCH 2/2] Char: applicom, use pci_match_id Jiri Slaby
2008-01-30 23:10 ` Andrew Morton
2008-01-31 9:26 ` Jiri Slaby
2008-01-26 9:57 ` [Patch] Shut up warnings from files under drivers/ Sam Ravnborg
2008-01-26 10:15 ` WANG Cong
2008-01-26 10:21 ` Sam Ravnborg
2008-01-26 10:26 ` WANG Cong
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=479B1D30.20501@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 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.