From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>, David Howells <dhowells@redhat.com>
Subject: [PATCH -next] samples: watch_queue: depends on HEADERS_INSTALL
Date: Thu, 10 Oct 2019 08:30:29 -0700 [thread overview]
Message-ID: <32afa048-0b12-ce26-2bb0-7672dca8ffb8@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Building samples/watch_queue/ uses installed headers, so make it
depends on HEADERS_INSTALL to prevent a build error.
../samples/watch_queue/watch_test.c:23:10: fatal error: linux/watch_queue.h: No such file or directory
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: David Howells <dhowells@redhat.com>
---
samples/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20191010.orig/samples/Kconfig
+++ linux-next-20191010/samples/Kconfig
@@ -171,6 +171,7 @@ config SAMPLE_VFS
config SAMPLE_WATCH_QUEUE
bool "Build example /dev/watch_queue notification consumer"
+ depends on HEADERS_INSTALL
help
Build example userspace program to use the new mount_notify(),
sb_notify() syscalls and the KEYCTL_WATCH_KEY keyctl() function.
next reply other threads:[~2019-10-10 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:30 Randy Dunlap [this message]
2019-10-11 7:54 ` David Howells
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=32afa048-0b12-ce26-2bb0-7672dca8ffb8@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®