linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the input tree
Date: Sat, 17 Oct 2015 09:39:30 -0700	[thread overview]
Message-ID: <20151017163930.GC13470@dtor-ws> (raw)
In-Reply-To: <5620A93E.40508@redhat.com>

On Fri, Oct 16, 2015 at 09:37:34AM +0200, Hans de Goede wrote:
> Hio,
> 
> On 16-10-15 04:19, Stephen Rothwell wrote:
> >Hi Dmitry,
> >
> >After merging the input tree, today's linux-next build (x86_64
> >allmodconfig) failed like this:
> >
> >In file included from samples/hidraw/hid-example.c:14:0:
> >./usr/include/linux/input.h:17:31: fatal error: input-event-codes.h: No such file or directory
> >
> >Caused by commit
> >
> >   d794709c3916 ("Input: Add input-event-codes header file")
> >
> >I have used the input tree from next-20151015 for today.
> 
> Sorry, my bad, I assumed anything under include/uapi would
> automatically get installed as a usr header, but it turns out
> any files added need to also be added to the Kbuild file, the
> attached patch should fix this.
> 
> Dmitry, feel free to squash this into the original patch.

Thanks Hans, I folded it into the original patch.

> 
> Regards,
> 
> Hans

> From 0dd5544b6ca0cddfe25976b46ef9ba5c4adbc791 Mon Sep 17 00:00:00 2001
> From: Hans de Goede <hdegoede@redhat.com>
> Date: Fri, 16 Oct 2015 09:33:45 +0200
> Subject: [PATCH] input: Add input-event-codes.h to usr headers to install
> 
> Add input-event-codes.h to the list of uapi headers to install, this fixes
> build-failures of any userspace tools including linux/input.h .
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
>  include/uapi/linux/Kbuild | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/uapi/linux/Kbuild b/include/uapi/linux/Kbuild
> index f7b2db4..0f26309 100644
> --- a/include/uapi/linux/Kbuild
> +++ b/include/uapi/linux/Kbuild
> @@ -191,6 +191,7 @@ header-y += inet_diag.h
>  header-y += in.h
>  header-y += inotify.h
>  header-y += input.h
> +header-y += input-event-codes.h
>  header-y += in_route.h
>  header-y += ioctl.h
>  header-y += ip6_tunnel.h
> -- 
> 2.5.0
> 


-- 
Dmitry

  reply	other threads:[~2015-10-17 16:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  2:19 linux-next: build failure after merge of the input tree Stephen Rothwell
2015-10-16  7:37 ` Hans de Goede
2015-10-17 16:39   ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-02  3:47 Stephen Rothwell
2025-07-02  4:01 ` Dmitry Torokhov
2022-10-24 23:00 Stephen Rothwell
2022-10-25  5:02 ` Dmitry Torokhov
2022-08-17  0:00 Stephen Rothwell
2022-08-17  0:07 ` Stephen Rothwell
2022-08-17  4:43 ` Uwe Kleine-König
2022-08-01 21:44 broonie
2022-08-04 12:33 ` Mark Brown
2022-08-04 23:36   ` Jiri Kosina
2022-04-27  0:48 Stephen Rothwell
2022-04-27  6:53 ` Fabien Parent
2022-04-27  7:35   ` Lee Jones
2022-04-27  7:41     ` Fabien Parent
2022-05-02  2:17 ` Stephen Rothwell
2022-05-06  0:25   ` Dmitry Torokhov
2022-05-31 10:13     ` Fabien Parent
2020-03-25  7:16 Stephen Rothwell
2020-03-31 21:06 ` Stephen Rothwell
2015-07-24  1:49 Stephen Rothwell
2015-07-24  2:33 ` Dmitry Torokhov
2012-10-05  1:47 Stephen Rothwell
2012-10-05  6:12 ` Dmitry Torokhov
2012-01-24  3:25 Stephen Rothwell
2012-01-24  6:59 ` Dmitry Torokhov
2012-01-24 23:16 ` John Stultz
2010-08-19  1:35 Stephen Rothwell
2010-08-19  5:19 ` Dmitry Torokhov

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=20151017163930.GC13470@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).