linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Arnd Bergmann <arnd@arndb.de>, Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Linus Walleij <linusw@kernel.org>,
	Enrico Weigelt <info@metux.net>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: apuv2: fix input dependencies
Date: Tue, 5 Mar 2019 15:56:15 +0200	[thread overview]
Message-ID: <CAHp75Vcd0eNCBtxb1huMBGFF9JXmropHv2YA1eh-yK3iMFfuFQ@mail.gmail.com> (raw)
In-Reply-To: <54a7d035-155f-c47b-1db1-acb851b3aec6@metux.net>

On Tue, Mar 5, 2019 at 3:50 PM Enrico Weigelt, metux IT consult
<lkml@metux.net> wrote:
> On 05.03.19 09:23, Arnd Bergmann wrote:

> > 1. try to use 'depends on' if you can
>
> Well, this has the unpleasant side effect that we often have to enable
> a lot of things, just to even see the individual driver. For people who
> just wanna configure a kernel for their board, this is a bit nasty.
>
> But, okay, I'm going to do this w/ my own tool - I've written a small
> tool that allows easy kernel reconfiguration on a higher level: you
> can just pick some board templates and enable high level features like
> eth, gpu, etc - it automatically creates a .config for you. I'm going
> announce it on lkml soon.

Darren gave a talk about merging kernel configs to get something like
you want to.
This tool is quite long already lying around. merge_config.sh in your
kernel source tree.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2019-03-05 13:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 20:19 [PATCH 1/3] x86: apuv2: remove unused variable Arnd Bergmann
2019-03-04 20:19 ` [PATCH 2/3] x86: apuv2: fix input dependencies Arnd Bergmann
2019-03-05  0:18   ` Enrico Weigelt, metux IT consult
2019-03-05  8:23     ` Arnd Bergmann
2019-03-05 13:50       ` Enrico Weigelt, metux IT consult
2019-03-05 13:56         ` Andy Shevchenko [this message]
2019-03-07  0:10           ` Enrico Weigelt, metux IT consult
2019-03-07  7:03             ` Darren Hart
2019-03-05 16:46         ` Arnd Bergmann
2019-03-04 20:19 ` [PATCH 3/3] x86: apuv2: select LEDS_CLASS Arnd Bergmann
2019-03-05  0:03   ` Enrico Weigelt, metux IT consult
2019-03-05  0:09     ` Randy Dunlap
2019-03-08  9:05       ` Linus Walleij
2019-03-05  0:04 ` [PATCH 1/3] x86: apuv2: remove unused variable Enrico Weigelt, metux IT consult
2019-03-05 13:47   ` Andy Shevchenko

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=CAHp75Vcd0eNCBtxb1huMBGFF9JXmropHv2YA1eh-yK3iMFfuFQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=arnd@arndb.de \
    --cc=dvhart@infradead.org \
    --cc=info@metux.net \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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).