linux-kernel - Re: [PATCH] char: remove VR41XX related char driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220716073748.GA9148@alpha.franken.de>
Date:   Sat, 16 Jul 2022 09:37:48 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] char: remove VR41XX related char driver

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@...ha.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 ]