All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v1 1/1] pinctrl: Sort Kconfig and Makefile entries alphabetically
Date: Thu, 9 Dec 2021 13:13:51 +0200	[thread overview]
Message-ID: <YbHk7wenlrhlizCA@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdb2ZnH7gi8TAQ_8hvbaAw=hqBZBjQftPOtyNMLR+c541g@mail.gmail.com>

On Thu, Dec 09, 2021 at 03:34:59AM +0100, Linus Walleij wrote:
> On Wed, Dec 8, 2021 at 10:20 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> 
> > Sort Kconfig and Makefile entries alphabetically for better maintenance
> > in the future.
> >
> > While at it fix some style issues, such as wrong indentation.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Nice! I tried to apply it but I was queueing patches from other
> unreviewed threads and creating misc problems.
> Ideally I'd like a patch close to the merge window,  but if
> you rebase this on linux-next (or the "devel" branch in my
> tree that I insist on using) I can try to apply it again anyways,

Sure.

> we need to take the hit at some point.

v2 just has been sent!

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v1 1/1] pinctrl: Sort Kconfig and Makefile entries alphabetically
Date: Thu, 9 Dec 2021 13:13:51 +0200	[thread overview]
Message-ID: <YbHk7wenlrhlizCA@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdb2ZnH7gi8TAQ_8hvbaAw=hqBZBjQftPOtyNMLR+c541g@mail.gmail.com>

On Thu, Dec 09, 2021 at 03:34:59AM +0100, Linus Walleij wrote:
> On Wed, Dec 8, 2021 at 10:20 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> 
> > Sort Kconfig and Makefile entries alphabetically for better maintenance
> > in the future.
> >
> > While at it fix some style issues, such as wrong indentation.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Nice! I tried to apply it but I was queueing patches from other
> unreviewed threads and creating misc problems.
> Ideally I'd like a patch close to the merge window,  but if
> you rebase this on linux-next (or the "devel" branch in my
> tree that I insist on using) I can try to apply it again anyways,

Sure.

> we need to take the hit at some point.

v2 just has been sent!

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v1 1/1] pinctrl: Sort Kconfig and Makefile entries alphabetically
Date: Thu, 9 Dec 2021 13:13:51 +0200	[thread overview]
Message-ID: <YbHk7wenlrhlizCA@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdb2ZnH7gi8TAQ_8hvbaAw=hqBZBjQftPOtyNMLR+c541g@mail.gmail.com>

On Thu, Dec 09, 2021 at 03:34:59AM +0100, Linus Walleij wrote:
> On Wed, Dec 8, 2021 at 10:20 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> 
> > Sort Kconfig and Makefile entries alphabetically for better maintenance
> > in the future.
> >
> > While at it fix some style issues, such as wrong indentation.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Nice! I tried to apply it but I was queueing patches from other
> unreviewed threads and creating misc problems.
> Ideally I'd like a patch close to the merge window,  but if
> you rebase this on linux-next (or the "devel" branch in my
> tree that I insist on using) I can try to apply it again anyways,

Sure.

> we need to take the hit at some point.

v2 just has been sent!

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-09 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  9:20 [PATCH v1 1/1] pinctrl: Sort Kconfig and Makefile entries alphabetically Andy Shevchenko
2021-12-08  9:20 ` Andy Shevchenko
2021-12-08  9:20 ` Andy Shevchenko
2021-12-09  2:34 ` Linus Walleij
2021-12-09  2:34   ` Linus Walleij
2021-12-09  2:34   ` Linus Walleij
2021-12-09 11:13   ` Andy Shevchenko [this message]
2021-12-09 11:13     ` Andy Shevchenko
2021-12-09 11:13     ` 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=YbHk7wenlrhlizCA@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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 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.