From: Konrad Zapalowicz <bergo.torino@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jslaby@suse.cz, cascardo@linux.vnet.ibm.com, markh@compro.net,
devel@driverdev.osuosl.org, lidza.louina@gmail.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 3/4] staging: dgnc: Remove driver in favor of serial/jsm driver
Date: Fri, 7 Nov 2014 00:36:23 +0100 [thread overview]
Message-ID: <20141106233623.GJ29761@t400> (raw)
In-Reply-To: <20141106232012.GA8585@kroah.com>
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@gmail.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.
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?
> So you will have to resend this later on when that happens.
Perfect
cheers,
konrad
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2014-11-06 23:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 0:06 [PATCH 0/5] serial: jsm: Add support for the Digi Classic adapters Konrad Zapalowicz
2014-11-03 0:06 ` [PATCH 1/5] drivers: serial: jsm: Add Classic board UART structure Konrad Zapalowicz
2014-11-03 0:06 ` [PATCH 2/5] drivers: serial: jsm: Add the Classic board implementation Konrad Zapalowicz
2014-11-03 0:06 ` [PATCH 3/5] drivers: serial: jsm: Enable support for Digi Classic adapters Konrad Zapalowicz
2014-11-03 0:06 ` [PATCH 4/5] staging: dgnc: Remove driver in favor of serial/jsm driver Konrad Zapalowicz
2014-11-03 0:06 ` [PATCH 5/5] drivers: serial: jsm: Remove FSF address from the file documentation/header Konrad Zapalowicz
2014-11-03 9:38 ` [PATCH 0/5] serial: jsm: Add support for the Digi Classic adapters Dan Carpenter
2014-11-03 18:52 ` [PATCH 1/5] drivers: serial: jsm: Add Classic board UART structure Konrad Zapalowicz
2014-11-03 18:52 ` [PATCH 2/5] drivers: serial: jsm: Add the Classic board implementation Konrad Zapalowicz
2014-11-03 18:52 ` [PATCH 3/5] drivers: serial: jsm: Enable support for Digi Classic adapters Konrad Zapalowicz
2014-11-03 18:52 ` [PATCH 4/5] staging: dgnc: Remove driver in favor of serial/jsm driver Konrad Zapalowicz
2014-11-06 19:18 ` [PATCH 2/5] drivers: serial: jsm: Add the Classic board implementation Greg KH
2014-11-06 23:05 ` [PATCH v2 0/4] serial: jsm: Add support for the Digi Classic adapters Konrad Zapalowicz
2014-11-06 23:05 ` [PATCH v2 1/4] drivers: serial: jsm: Add the Classic board implementation Konrad Zapalowicz
2014-11-06 23:05 ` [PATCH v2 2/4] drivers: serial: jsm: Enable support for Digi Classic adapters Konrad Zapalowicz
2014-11-06 23:05 ` [PATCH v2 3/4] staging: dgnc: Remove driver in favor of serial/jsm driver Konrad Zapalowicz
2014-11-06 23:05 ` [PATCH v2 4/4] drivers: serial: jsm: Remove FSF address from the file documentation/header Konrad Zapalowicz
2014-11-06 23:20 ` [PATCH v2 3/4] staging: dgnc: Remove driver in favor of serial/jsm driver Greg KH
2014-11-06 23:36 ` Konrad Zapalowicz [this message]
2014-11-07 16:12 ` Greg KH
2014-11-06 23:11 ` [PATCH 2/5] drivers: serial: jsm: Add the Classic board implementation Konrad Zapalowicz
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=20141106233623.GJ29761@t400 \
--to=bergo.torino@gmail.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=markh@compro.net \
/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