From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char: remove VR41XX related char driver
Date: Sat, 16 Jul 2022 09:37:48 +0200 [thread overview]
Message-ID: <20220716073748.GA9148@alpha.franken.de> (raw)
In-Reply-To: <YtJP+k5JBbqS5QgY@kroah.com>
On Sat, Jul 16, 2022 at 07:43:22AM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 15, 2022 at 04:24:36PM +0200, Thomas Bogendoerfer wrote:
> > 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>
> > ---
> > drivers/char/Kconfig | 5 -
> > drivers/char/Makefile | 1 -
> > drivers/char/tb0219.c | 358 ------------------------------------------
> > 3 files changed, 364 deletions(-)
> > delete mode 100644 drivers/char/tb0219.c
>
> This does not apply to my tree, what tree did you make it against?
I've used linux-next.
> Nothing has touched the drivers/char/tb0219.c file in a very long time,
there is commit c9d86760342f ("fs: do not set no_llseek in fops") in
linux-next, which touches it.
> perhaps you might want to wait for this driver removal series until
> after d3164e2f3b0a is merged into Linus's tree?
I'll respin against your tree.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-07-16 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 14:24 Thomas Bogendoerfer
2022-07-16 5:43 ` Greg Kroah-Hartman
2022-07-16 7:37 ` 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=20220716073748.GA9148@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®