linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpio: remove VR41XX related gpio driver
Date: Fri, 15 Jul 2022 16:31:40 +0200	[thread overview]
Message-ID: <20220715143140.GA4809@alpha.franken.de> (raw)
In-Reply-To: <YtF0Xt0Ja9biwwnt@kroah.com>

On Fri, Jul 15, 2022 at 04:06:22PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 15, 2022 at 03:59:44PM +0200, Thomas Bogendoerfer wrote:
> > From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> > 
> > Commit d3164e2f3b0a ("MIPS: Remove VR41xx support") removed support
> > for MIPS VR41xx platform, so remove exclusive drivers for this
> > platform, too.
> > 
> > Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> > Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> > ---
> >  drivers/char/Kconfig       |   5 -
> >  drivers/char/Makefile      |   1 -
> >  drivers/char/tb0219.c      | 358 ------------------------
> >  drivers/gpio/Kconfig       |   6 -
> >  drivers/gpio/Makefile      |   1 -
> >  drivers/gpio/gpio-vr41xx.c | 541 -------------------------------------
> >  6 files changed, 912 deletions(-)
> >  delete mode 100644 drivers/char/tb0219.c
> >  delete mode 100644 drivers/gpio/gpio-vr41xx.c
> 
> This should be 2 patches, one for the char driver and one for the gpio
> driver.

sure, new patches sent.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2022-07-15 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 13:59 [PATCH] gpio: remove VR41XX related gpio driver Thomas Bogendoerfer
2022-07-15 14:06 ` Greg Kroah-Hartman
2022-07-15 14:31   ` Thomas Bogendoerfer [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=20220715143140.GA4809@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).