All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/2] Clean all defconfigs with savedefconfig
Date: Mon, 01 Jun 2015 10:46:52 +0100	[thread overview]
Message-ID: <1433152012.15036.86.camel@hellion.org.uk> (raw)
In-Reply-To: <CAGb2v66G18g3NKkczRMZe=u0B5GH-F76JdX8HHQ3iWUd+TGx8Q@mail.gmail.com>

On Mon, 2015-06-01 at 15:45 +0800, Chen-Yu Tsai wrote:
> Hi,
> 
> On Wed, May 13, 2015 at 6:12 AM, Tom Rini <trini@konsulko.com> wrote:
> > On Tue, May 12, 2015 at 02:46:24PM -0500, Joe Hershberger wrote:
> >
> >> In order to reduce merge conflicts and to maintain the simplest possible
> >> defconfig files, we should be using the savedefconfig feature of Kconfig
> >> every time a new feature is added. This keeps the defconfig settings to
> >> a minimum (only those things not default) and keeps them in the same
> >> order as the Kconfig options.
> >>
> >> Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
> >> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> >> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
> >> Cc: Tom Rini <trini@konsulko.com>
> >>
> >
> > Applied to u-boot/master, thanks!
> 
> This patch wiped out all comments we had in sunxi defconfigs.
> The comments include description for the boards, a link to a
> wiki page, explanations for regulator and gpio settings.
> 
> Hans, Ian, should we move that info to some other place that's
> safer?

The information is certainly useful and should be preserved. If we can't
arrange for savedefconfig to preserve useful information (my preference)
we should indeed put it somewhere else, but where? MAINTAINERS files
perhaps?

Tom -- perhaps in the meantime we could get a partial revert?

Ian.

  reply	other threads:[~2015-06-01  9:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 17:08 [U-Boot] [PATCH] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-11 18:32 ` Joe Hershberger
2015-05-12 15:18   ` Tom Rini
2015-05-12 16:20     ` Joe Hershberger
2015-05-12 16:32       ` Tom Rini
2015-05-13  1:24         ` Masahiro Yamada
2015-05-13  3:33           ` Joe Hershberger
2015-05-11 20:02 ` Stephen Warren
2015-05-11 20:17   ` Joe Hershberger
2015-05-11 21:07     ` Stephen Warren
2015-05-12  4:19       ` Joe Hershberger
2015-05-12 18:01 ` [U-Boot] [PATCH v2 1/2] kconfig: Make board selection choices optional Joe Hershberger
2015-05-12 18:01   ` [U-Boot] [PATCH v2 2/2] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-12 19:31   ` [U-Boot] [PATCH v2 1/2] kconfig: Make board selection choices optional Stephen Warren
2015-05-12 19:34     ` Joe Hershberger
2015-05-12 19:46   ` [U-Boot] [PATCH v3 1/2] arch: " Joe Hershberger
2015-05-12 19:46     ` [U-Boot] [PATCH v3 2/2] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-12 22:12       ` Tom Rini
2015-06-01  7:45         ` Chen-Yu Tsai
2015-06-01  9:46           ` Ian Campbell [this message]
2015-06-01 13:41             ` Joe Hershberger
2015-06-01 14:12               ` Tom Rini
2015-05-12 21:55     ` [U-Boot] [PATCH v3 1/2] arch: Make board selection choices optional Stephen Warren
2015-05-12 22:06       ` Joe Hershberger
2015-05-12 22:12     ` Tom Rini
2015-05-13  1:11       ` Masahiro Yamada
2015-07-29 17:25         ` Alexey Brodkin
2015-07-29 17:32           ` Alexey Brodkin
2015-08-01  7:46             ` Masahiro Yamada

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=1433152012.15036.86.camel@hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=u-boot@lists.denx.de \
    /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.