From: Linus Walleij <linus.walleij@linaro.org>
To: Laura Abbott <labbott@redhat.com>, openwrt-devel@openwrt.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND][PATCH] config: Add Fedora config fragments
Date: Fri, 7 Apr 2017 09:40:47 +0200 [thread overview]
Message-ID: <CACRpkdaz8kASd1XQYchj2uybo3nKeeNqfbQ4RpRNFeDxgdn2uA@mail.gmail.com> (raw)
In-Reply-To: <1491257994-23350-1-git-send-email-labbott@redhat.com>
On Tue, Apr 4, 2017 at 12:19 AM, Laura Abbott <labbott@redhat.com> wrote:
> Based on feedback, Fedora is a popular distribution for people who like
> to build their own kernels. To make this easier, add a set of
> reasonablly common config options for Fedora.
>
> fedora-core.config contains a base set of options that should work on a
> standard fedora system. fedora-fs.config and fedora-networking.config
> contain more options for those subsystems.
>
> Signed-off-by: Laura Abbott <labbott@redhat.com>
I would use this, so:
Acked-by: Linus Walleij <linus.walleij@linaro.org>
I hacked up fragments for using Arch Linux and I believe OpenWRT
could use fragments like this as well.
I think we should discuss feature splitting of the config fragments.
What is complicated with configs is finding the right kernel features
for the userspace you are doing. At one point, I don't remember where
or when, it was discussed adding a systemd config fragment, as it
is using a slew of non-optional kernel config options. Then other
distros using that could simply use that fragment to get it right.
I'm pretty sure the systemd deps are a subset of the Fedora config
for example.
I would think similar fragments could be good for e.g. wireless
networking, USB storage and such things where I for one found
it really annoying having to spend time finding the right Kconfig to
just get that rolling reasonably.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-04-07 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 22:19 [RESEND][PATCH] config: Add Fedora config fragments Laura Abbott
2017-04-07 7:40 ` Linus Walleij [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=CACRpkdaz8kASd1XQYchj2uybo3nKeeNqfbQ4RpRNFeDxgdn2uA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openwrt-devel@openwrt.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).