From: Al Viro <viro@ftp.linux.org.uk>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Len Brown <len.brown@intel.com>,
zippel@linux-m68k.org, viro@ZenIV.linux.org.uk,
Eric.Piel@lifl.fr, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bogus #if (acpi/blacklist)
Date: Thu, 22 Sep 2005 06:15:57 +0100 [thread overview]
Message-ID: <20050922051557.GH7992@ftp.linux.org.uk> (raw)
In-Reply-To: <20050921221426.7ccdeac7.rdunlap@xenotime.net>
On Wed, Sep 21, 2005 at 10:14:26PM -0700, Randy.Dunlap wrote:
> obj-y += tables.o
> +ifdef CONFIG_X86
> obj-y += blacklist.o
> +endif
More common form would be
obj-$(CONFIG_X86) += blacklist.o
next prev parent reply other threads:[~2005-09-22 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 16:07 [PATCH] bogus #if (acpi/blacklist) viro
2005-09-09 16:19 ` Eric Piel
2005-09-09 16:43 ` viro
2005-09-09 16:55 ` Roman Zippel
2005-09-09 17:31 ` viro
2005-09-15 22:05 ` Len Brown
2005-09-22 5:14 ` Randy.Dunlap
2005-09-22 5:15 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 5:50 Brown, Len
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=20050922051557.GH7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=Eric.Piel@lifl.fr \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@osdl.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=zippel@linux-m68k.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