All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Alexander Dahl <post@lespocky.de>
Cc: "Michal Simek" <michal.simek@amd.com>,
	u-boot@lists.denx.de, "Alexander Dahl" <ada@thorsis.com>,
	"Wolfgang Wegner" <w.wegner@astro-kom.de>,
	"Simon Glass" <sjg@chromium.org>, "Stefan Roese" <sr@denx.de>,
	"Patrick Delaunay" <patrick.delaunay@foss.st.com>,
	"Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH v2 2/2] fpga: Convert SYS_FPGA_PROG_FEEDBACK to Kconfig
Date: Wed, 13 Jul 2022 10:19:21 -0400	[thread overview]
Message-ID: <20220713141921.GD1146598@bill-the-cat> (raw)
In-Reply-To: <20220713131109.GA1941@falbala.internal.home.lespocky.de>

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

On Wed, Jul 13, 2022 at 03:11:09PM +0200, Alexander Dahl wrote:
> Hei hei,
> 
> On Wed, Jul 13, 2022 at 02:50:14PM +0200, Michal Simek wrote:
> > 
> > 
> > On 7/13/22 14:33, Alexander Dahl wrote:
> > > From: Alexander Dahl <ada@thorsis.com>
> > 
> > 
> > WARNING: please write a paragraph that describes the config symbol fully
> > 
> > We don't allow patches with empty commit message.
> 
> In general I would agree.  However several of Tom's patches addressing
> kconfig migration have a commit message like this:
> 
>   This converts the following to Kconfig: FOO_BAR
> 
> This is redundant to the subject saying exactly the same.  I can add
> this if you want, but I saw no sense in it.

Yes, the moveconfig.py tool adds that and it's a little redundant
sometimes, but is (a) a starting point for the times when the conversion
required a little extra work or (b) lists all the symbols when you
migrate more than one at a time.

> > > Signed-off-by: Alexander Dahl <ada@thorsis.com>
> > > ---
> > >   README                           | 4 ----
> > >   configs/astro_mcf5373l_defconfig | 1 +
> > >   drivers/fpga/Kconfig             | 6 ++++++
> > >   include/configs/astro_mcf5373l.h | 1 -
> > >   scripts/config_whitelist.txt     | 1 -
> > 
> > Tom can confirm this but IIRC you don't need to remove this from this file.
> > Tom is doing sync up time to time. It is enough to do conversion only.
> 
> This was done by the script ./tools/moveconfig.py where I just hit
> enter with defaults presented.  The other Kconfig patches change
> defconfig, but not whitelist.  Seems a little inconsistent to me.  But
> I can remove that part, sure.

So, I usually run "-yC" with moveconfig.py as that gives the commit
message.  It's not a problem, really, to touch
scripts/config_whitelist.txt it just also can conflict easily.  Omitting
it makes it easier to "git am", fixing up / dropping that hunk if it
conflicts later is also fine.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2022-07-13 14:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 12:32 [PATCH v2 0/2] fpga: Convert some options to Kconfig Alexander Dahl
2022-07-13 12:32 ` [PATCH v2 1/2] fpga: Convert SYS_FPGA_CHECK_CTRLC " Alexander Dahl
2022-07-13 12:56   ` Michal Simek
2022-07-13 13:20     ` Alexander Dahl
2022-07-13 13:53       ` Michal Simek
2022-07-13 14:07       ` Alexander Dahl
2022-07-13 14:18         ` Michal Simek
2022-07-13 14:19       ` Tom Rini
2022-07-13 12:33 ` [PATCH v2 2/2] fpga: Convert SYS_FPGA_PROG_FEEDBACK " Alexander Dahl
2022-07-13 12:50   ` Michal Simek
2022-07-13 13:11     ` Alexander Dahl
2022-07-13 14:19       ` Tom Rini [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=20220713141921.GD1146598@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=ada@thorsis.com \
    --cc=marek.behun@nic.cz \
    --cc=michal.simek@amd.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=post@lespocky.de \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=w.wegner@astro-kom.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.