public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 defconfig updates for v4.6 #1
Date: Thu, 03 Mar 2016 11:33:34 +0100	[thread overview]
Message-ID: <1624048.IcI7yXPN7a@wuerfel> (raw)
In-Reply-To: <CALszF6Cgng3Yr_vrag7LY9zYunV_Fca0oHKX45w6t29DFqC5gA@mail.gmail.com>

On Thursday 03 March 2016 09:59:35 Maxime Coquelin wrote:
> 2016-03-02 23:21 GMT+01:00 Arnd Bergmann <arnd@arndb.de>:
> > On Wednesday 02 March 2016 11:53:23 Maxime Coquelin wrote:
> >> Highlights:
> >> -----------
> >>   - Enable GPIO led driver in stm32_defconfig
> >>   - Introduce a config fragment to override RAM base address
> >>
> >
> > Our first config fragment 
> 
> Yes! Out of curiosity, did you see the question I asked you about fragments?
> See "Re: [PATCH v3 4/4] ARM: STM32: Enable Ethernet in stm32_defconfig".
> (https://lkml.org/lkml/2016/3/1/474)
> 
> This is not urgent, it can wait for after the merge window, but I will
> be happy to have your view on this.
> 

No, I missed that. Generally, I'd say we should limit the use of Kconfig
fragments to more fundamental settings, it should not replace the
manual configuration that users apply to pick the set of drivers
they want. In the end there is not much difference between someone
locally turning on CONFIG_INET when they need it, or using a fragment
that does the same.

Please just pick one default here (ethernet and ipv4 both enabled or
both disabled) that makes sense for most users, and have the others
change it manually.

	Arnd

  reply	other threads:[~2016-03-03 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 10:53 [GIT PULL] STM32 defconfig updates for v4.6 #1 Maxime Coquelin
2016-03-02 22:21 ` Arnd Bergmann
2016-03-03  8:59   ` Maxime Coquelin
2016-03-03 10:33     ` Arnd Bergmann [this message]
2016-03-03 13:09       ` Maxime Coquelin

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=1624048.IcI7yXPN7a@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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