All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Arnd Bergmann <arnd@arndb.de>,
	"D, Lakshmi Sowjanya" <lakshmi.sowjanya.d@intel.com>
Subject: Re: [GIT PULL] pin control changes for v5.17
Date: Wed, 12 Jan 2022 22:56:12 +0200	[thread overview]
Message-ID: <Yd9AbO+Id7y1+IY+@smile.fi.intel.com> (raw)
In-Reply-To: <Yd88UBp9uaDSc2qW@smile.fi.intel.com>

On Wed, Jan 12, 2022 at 10:38:40PM +0200, Andy Shevchenko wrote:
> On Wed, Jan 12, 2022 at 11:09:23AM -0800, Linus Torvalds wrote:
> > On Wed, Jan 12, 2022 at 3:23 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > >
> > > - There will be conflicts! Kconfig and Makefile conflicts due to
> > >   some RISC-V Starfive patches getting merged through the
> > >   SoC tree while we were tidying up the Kconfig and Makefile
> > >   (to avoid merge conflicts, heh) there is a resolution in linux-next
> > >   which was discussed and reviewed to be correct.
> > 
> > Whoever sorted the Makefile entries (yeah, it was Andy) isn't very good at it.
> 
> Indeed. Sorry for that, I will send an update for next cycle.
> 
> > The broken sorting put CONFIG_PINCTRL_STMFX before CONFIG_PINCTRL_ST,
> > and I have no idea how you can sort that way.
> > 
> > I left the broken sorting in place, because changing the sort order in
> > the merge would just be even *more* confusing.
> > 
> > There may be other cases of that kind of oddity, I just happened to
> > notice that one because the 'starfive' thing ended up having that same
> > 'st' beginning, and I went D'Oh when trying to make sure my merge kept
> > the ordering.


I setup a little experiment, since I'm using vim, there are two possibilities
to sort the selection, i.e. using internal sort and calling external !sort.

Using internal gives:

-obj-$(CONFIG_PINCTRL_STMFX)    += pinctrl-stmfx.o
 obj-$(CONFIG_PINCTRL_ST)       += pinctrl-st.o
 obj-$(CONFIG_PINCTRL_STARFIVE) += pinctrl-starfive.o
+obj-$(CONFIG_PINCTRL_STMFX)    += pinctrl-stmfx.o


Using external gives:

+obj-$(CONFIG_PINCTRL_STARFIVE) += pinctrl-starfive.o
 obj-$(CONFIG_PINCTRL_STMFX)    += pinctrl-stmfx.o
 obj-$(CONFIG_PINCTRL_ST)       += pinctrl-st.o
-obj-$(CONFIG_PINCTRL_STARFIVE) += pinctrl-starfive.o


Now you may easily see what happened.


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-01-12 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 11:23 [GIT PULL] pin control changes for v5.17 Linus Walleij
2022-01-12 19:09 ` Linus Torvalds
2022-01-12 20:38   ` Andy Shevchenko
2022-01-12 20:56     ` Andy Shevchenko [this message]
2022-01-12 21:02       ` Linus Torvalds
2022-01-12 19:12 ` pr-tracker-bot

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=Yd9AbO+Id7y1+IY+@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=lakshmi.sowjanya.d@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.