All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rob Landley <rob@landley.net>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	linux-sh@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v1] sh: Drop ARCH_NR_GPIOS definition
Date: Mon, 28 Dec 2020 23:36:15 +0200	[thread overview]
Message-ID: <20201228213615.GF4077@smile.fi.intel.com> (raw)
In-Reply-To: <10b4dc8e-db87-3f78-3ab7-e08469b9fe55@landley.net>

On Wed, Nov 11, 2020 at 10:45:38AM -0600, Rob Landley wrote:
> On 11/9/20 6:13 AM, Andy Shevchenko wrote:
> > On Mon, Oct 12, 2020 at 06:40:50PM +0300, Andy Shevchenko wrote:
> >> The default by generic header is the same, hence drop unnecessary definition.
> > 
> > Any comment on this?
> 
> Acked-by: Rob Landley <rob@landley.net>

Thanks!

> It's in the stack I forwarded to Rich to look at this weekend.

Unfortunately I still do not see this in the latest Linux Next.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-12-28 23:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 15:40 [PATCH v1] sh: Drop ARCH_NR_GPIOS definition Andy Shevchenko
2020-10-12 15:40 ` Andy Shevchenko
2020-11-09 12:13 ` Andy Shevchenko
2020-11-09 12:13   ` Andy Shevchenko
2020-11-11 16:45   ` Rob Landley
2020-11-11 16:45     ` Rob Landley
2020-12-28 21:36     ` Andy Shevchenko [this message]
2021-01-01 13:51       ` John Paul Adrian Glaubitz
2021-01-02  2:12         ` Rob Landley
2021-01-18 20:20           ` John Paul Adrian Glaubitz
2021-01-18 23:44             ` Rob Landley
2021-01-01 14:24 ` John Paul Adrian Glaubitz
2021-01-18 20:11 ` John Paul Adrian Glaubitz

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=20201228213615.GF4077@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=dalias@libc.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=ysato@users.sourceforge.jp \
    /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.