From: Greg KH <gregkh@linuxfoundation.org>
To: Rolf Eike Beer <eb@emlix.com>
Cc: stable@vger.kernel.org, Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH 4.9.y 2/2] install several missing uapi headers
Date: Sun, 2 Aug 2020 09:04:07 +0200 [thread overview]
Message-ID: <20200802070407.GB3889624@kroah.com> (raw)
In-Reply-To: <2892097.ECyh5nn9PN@devpool35>
On Thu, Jul 30, 2020 at 03:01:45PM +0200, Rolf Eike Beer wrote:
> Commit fcc8487d477a3452a1d0ccbdd4c5e0e1e3cb8bed ("uapi: export all headers
> under uapi directories") changed the default to install all headers not marked
> to be conditional. This takes the list of headers listed in the commit message
> and manually adds an export for those that are already present in this kernel
> version.
>
> Found during an attempt to build mtd-utils 2.1.2 as it wants hash_info.h, which
> exists since 3.13 but has not been installed until the above mentioned commit,
> which ended up in 4.12.
>
> Signed-off-by: Rolf Eike Beer <eb@emlix.com>
> ---
> arch/mips/include/uapi/asm/Kbuild | 3 +++
> arch/powerpc/include/uapi/asm/Kbuild | 1 +
> include/uapi/drm/Kbuild | 3 +++
> include/uapi/linux/Kbuild | 20 ++++++++++++++++++++
> include/uapi/linux/cifs/Kbuild | 2 ++
> include/uapi/linux/genwqe/Kbuild | 2 ++
> 6 files changed, 31 insertions(+)
> create mode 100644 include/uapi/linux/cifs/Kbuild
> create mode 100644 include/uapi/linux/genwqe/Kbuild
I doubt many people are hitting this old issue on 4.9, but oh well, it
looks correct, so now queued up :)
greg k-h
prev parent reply other threads:[~2020-08-02 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 12:59 [PATCH 4.9.y 1/2] uapi: includes linux/types.h before exporting files Rolf Eike Beer
2020-07-30 13:01 ` [PATCH 4.9.y 2/2] install several missing uapi headers Rolf Eike Beer
2020-08-02 7:04 ` Greg KH [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=20200802070407.GB3889624@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eb@emlix.com \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).