From: Adrian Bunk <bunk@stusta.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Kbuild: add 3 more header files to get properly "unifdef"ed
Date: Sun, 3 Dec 2006 23:12:03 +0100 [thread overview]
Message-ID: <20061203221203.GC3442@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0611300459290.12927@localhost.localdomain>
On Thu, Nov 30, 2006 at 05:03:56AM -0500, Robert P. J. Day wrote:
>
> Add 3 more files to get "unifdef"ed when creating sanitized headers
> with "make headers_install".
Your patch should also remove them from header-y.
> Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
>
> ---
>
> diff --git a/include/linux/Kbuild b/include/linux/Kbuild
> index a1155a2..b6bc50c 100644
> --- a/include/linux/Kbuild
> +++ b/include/linux/Kbuild
> @@ -225,6 +225,7 @@ unifdef-y += if_bridge.h
> unifdef-y += if_ec.h
> unifdef-y += if_eql.h
> unifdef-y += if_ether.h
> +unifdef-y += if_fddi.h
> unifdef-y += if_frad.h
> unifdef-y += if_ltalk.h
> unifdef-y += if_pppox.h
> @@ -286,6 +287,7 @@ unifdef-y += nvram.h
> unifdef-y += parport.h
> unifdef-y += patchkey.h
> unifdef-y += pci.h
> +unifdef-y += personality.h
> unifdef-y += pktcdvd.h
> unifdef-y += pmu.h
> unifdef-y += poll.h
> @@ -341,6 +343,7 @@ unifdef-y += videodev.h
> unifdef-y += wait.h
> unifdef-y += wanrouter.h
> unifdef-y += watchdog.h
> +unifdef-y += wireless.h
> unifdef-y += xfrm.h
> unifdef-y += zftape.h
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-12-03 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 10:03 [PATCH] Kbuild: add 3 more header files to get properly "unifdef"ed Robert P. J. Day
2006-12-03 22:12 ` Adrian Bunk [this message]
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=20061203221203.GC3442@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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