From: Daniel Borkmann <daniel@iogearbox.net>
To: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH] EXPERT Kconfig menu: fix broken EXPERT menu
Date: Fri, 03 Nov 2017 00:34:49 +0100 [thread overview]
Message-ID: <59FBAB99.9070100@iogearbox.net> (raw)
In-Reply-To: <72e4465a-a5ff-cb3c-1a90-11aa4861b161@infradead.org>
On 11/03/2017 12:07 AM, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Clean up the EXPERT menu (yet again).
>
> Move FHANDLE and CHECKPOINT_RESTORE into the primary EXPERT menu
> since they already depend on EXPERT.
>
> Move BPF_SYSCALL and USERFAULTFD out of the EXPERT Kconfig symbols
> menu list since they do not depend on EXPERT and were breaking the
> continuity of that menu list.
>
> Move all of the KALLSYMS Kconfig symbols to the end of the EXPERT
> menu. This separates the kernel services from the build options.
>
> This patch depends on [PATCH] pci: move PCI_QUIRKS to the PCI bus menu
> (https://lkml.org/lkml/2017/11/2/907).
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Andrea Arcangeli <aarcange@redhat.com>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
For BPF bits:
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
prev parent reply other threads:[~2017-11-02 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 23:07 [PATCH] EXPERT Kconfig menu: fix broken EXPERT menu Randy Dunlap
2017-11-02 23:34 ` Daniel Borkmann [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=59FBAB99.9070100@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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 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.