public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
	gregkh@suse.de, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org, jirislaby@gmail.com,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Alan Cox <alan@linux.intel.com>,
	linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 4/4] TTY: serial, move 68360 driver to staging
Date: Wed, 31 Aug 2011 12:41:31 -0700	[thread overview]
Message-ID: <20110831194131.GB14091@kroah.com> (raw)
In-Reply-To: <1314819086.30506.3.camel@lappy>

On Wed, Aug 31, 2011 at 10:31:26PM +0300, Sasha Levin wrote:
> On Wed, 2011-08-31 at 21:24 +0200, Jiri Slaby wrote:
> > This driver has been broken at least since 2008. At that time,
> > a88487c79b (Fix compile errors in SGI console drivers) broke this
> > driver completely.
> > 
> > And since nobody noticed for the past 3 years, move it into staging. I
> > think this will rot there and we will throw it away completely after
> > some time. Or maybe someone will volunteer to fix it ;).
> > 
> > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> > Cc: Alan Cox <alan@linux.intel.com>
> > ---
> > Cc: linux-m68k@lists.linux-m68k.org
> >  drivers/staging/Kconfig              |    2 +
> >  drivers/staging/Makefile             |    1 +
> >  drivers/staging/serial/68360serial.c | 2979 ++++++++++++++++++++++++++++++++++
> >  drivers/staging/serial/Kconfig       |   16 +
> >  drivers/staging/serial/Makefile      |    1 +
> >  drivers/staging/serial/TODO          |    6 +
> >  drivers/tty/serial/68360serial.c     | 2979 ----------------------------------
> >  drivers/tty/serial/Kconfig           |   17 -
> >  drivers/tty/serial/Makefile          |    1 -
> >  9 files changed, 3005 insertions(+), 2997 deletions(-)
> >  create mode 100644 drivers/staging/serial/68360serial.c
> >  create mode 100644 drivers/staging/serial/Kconfig
> >  create mode 100644 drivers/staging/serial/Makefile
> >  create mode 100644 drivers/staging/serial/TODO
> >  delete mode 100644 drivers/tty/serial/68360serial.c
> 
> 'git mv' and 'git format-patch --find-renames' would make this patch so
> much nicer.

That will happen automatically when I apply the patch, so don't worry
about it.

greg k-h

      parent reply	other threads:[~2011-08-31 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1314818699-10873-1-git-send-email-jslaby@suse.cz>
2011-08-31 19:24 ` [PATCH 2/4] TTY: serial, remove dead code from 68328 Jiri Slaby
2011-08-31 19:51   ` Geert Uytterhoeven
     [not found]   ` <CAMuHMdUBYarp4V_k_8Skr8T-Ow2fc69EpJGi3wm-M_UZNxDLeA@mail.gmail.com>
2011-08-31 19:51     ` Geert Uytterhoeven
     [not found] ` <1314818699-10873-4-git-send-email-jslaby@suse.cz>
2011-08-31 19:31   ` [PATCH 4/4] TTY: serial, move 68360 driver to staging Sasha Levin
     [not found]   ` <1314819086.30506.3.camel@lappy>
2011-08-31 19:41     ` Greg KH [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=20110831194131.GB14091@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-serial@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