From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: 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, 09 Nov 2020 12:13:33 +0000 [thread overview] Message-ID: <20201109121333.GC4077@smile.fi.intel.com> (raw) In-Reply-To: <20201012154050.68039-1-andriy.shevchenko@linux.intel.com> 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? > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > --- > arch/sh/include/asm/gpio.h | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/sh/include/asm/gpio.h b/arch/sh/include/asm/gpio.h > index 351918894e86..d643250f0a0f 100644 > --- a/arch/sh/include/asm/gpio.h > +++ b/arch/sh/include/asm/gpio.h > @@ -16,7 +16,6 @@ > #include <cpu/gpio.h> > #endif > > -#define ARCH_NR_GPIOS 512 > #include <asm-generic/gpio.h> > > #ifdef CONFIG_GPIOLIB > -- > 2.28.0 > -- With Best Regards, Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: 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, 9 Nov 2020 14:13:33 +0200 [thread overview] Message-ID: <20201109121333.GC4077@smile.fi.intel.com> (raw) In-Reply-To: <20201012154050.68039-1-andriy.shevchenko@linux.intel.com> 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? > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > --- > arch/sh/include/asm/gpio.h | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/sh/include/asm/gpio.h b/arch/sh/include/asm/gpio.h > index 351918894e86..d643250f0a0f 100644 > --- a/arch/sh/include/asm/gpio.h > +++ b/arch/sh/include/asm/gpio.h > @@ -16,7 +16,6 @@ > #include <cpu/gpio.h> > #endif > > -#define ARCH_NR_GPIOS 512 > #include <asm-generic/gpio.h> > > #ifdef CONFIG_GPIOLIB > -- > 2.28.0 > -- With Best Regards, Andy Shevchenko
next prev parent reply other threads:[~2020-11-09 12: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 [this message] 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 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=20201109121333.GC4077@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=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: linkBe 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.