linux-kernel - Re: [PATCH v2 3/4] staging: dgnc: Remove driver in favor of serial/jsm 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: <20141107161258.GA12566@kroah.com>
Date:	Fri, 7 Nov 2014 08:12:58 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Konrad Zapalowicz <bergo.torino@...il.com>
Cc:	jslaby@...e.cz, cascardo@...ux.vnet.ibm.com, markh@...pro.net,
	devel@...verdev.osuosl.org, lidza.louina@...il.com,
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH v2 3/4] staging: dgnc: Remove driver in favor of
 serial/jsm driver

On Fri, Nov 07, 2014 at 12:36:23AM +0100, Konrad Zapalowicz wrote:
> On 11/06, Greg KH wrote:
> > On Fri, Nov 07, 2014 at 12:05:34AM +0100, Konrad Zapalowicz wrote:
> > > This commit removes the staging/dgnc driver in favor of the serial/jsm
> > > driver.
> > > 
> > > This is because the serial/jsm driver now supports all of the hardware
> > > that has been supported by the staging/dgnc plus it offers better
> > > overall quality.
> > > 
> > > Given above the staging/dgnc is obsolete now.
> > > 
> > > Signed-off-by: Konrad Zapalowicz <bergo.torino@...il.com>
> > 
> > I've applied the other patches in this series, but am going to skip this
> > one at the moment until I get some "it works for me" verification from
> > someone who has this hardware.
> 
> I will have some patches following-up this series, mostly fixing some
> minor stuff that I found going through the current jsm code plus the
> stuff that can now be shared between neo and cls code. So should I send
> it and it will end up in the tty testing tree or wait till my patches
> will make it to the next/mainline.

Please send them whenever you have them done and you feel they are
correct.

> In case you want the patches should I mark them somehow so that you know
> it is something that should go to the tty testing tree?

If you just send them saying it is against my tty-testing (or tty-next,
as your patches are now merged into that), it's fine.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/