From: Al Viro <viro@ZenIV.linux.org.uk>
To: zijun_hu <zijun_hu@zoho.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH 1/1] bitops.h: move out get_count_order[_long]() from __KERNEL__ scope
Date: Thu, 18 Aug 2016 01:28:08 +0100 [thread overview]
Message-ID: <20160818002808.GK2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <0ba55ab9-eae7-d50f-1b45-c6714e094b03@zoho.com>
On Thu, Aug 18, 2016 at 08:10:19AM +0800, zijun_hu wrote:
> Documentation/kbuild/makefiles.txt：
> The kernel includes a set of headers that is exported to userspace.
> Many headers can be exported as-is but other headers require a
> minimal pre-processing before they are ready for user-space.
> The pre-processing does:
> - drop kernel-specific annotations
> - drop include of compiler.h
> - drop all sections that are kernel internal (guarded by ifdef __KERNEL__)
>
> scripts/Makefile.headersinst:
> # ==========================================================================
> # Installing headers
> #
> # header-y - list files to be installed. They are preprocessed
> # to remove __KERNEL__ section of the file
> # genhdr-y - Same as header-y but in a generated/ directory
Quite. Now, could you show me where bitops.h is mentioned in any header-y
assignments?
Stuff outside of */uapi/* is not exported at all.
next prev parent reply other threads:[~2016-08-18 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 6:27 [PATCH 1/1] bitops.h: move out get_count_order[_long]() from __KERNEL__ scope zijun_hu
2016-08-16 6:50 ` Stephen Rothwell
2016-08-16 7:24 ` zijun_hu
2016-08-16 7:46 ` [RESEND PATCH " zijun_hu
2016-08-17 17:20 ` Al Viro
2016-08-17 23:51 ` zijun_hu
2016-08-17 23:59 ` Al Viro
2016-08-18 0:10 ` zijun_hu
2016-08-18 0:28 ` Al Viro [this message]
2016-08-18 0:50 ` zijun_hu
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=20160818002808.GK2356@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zijun_hu@zoho.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.