All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Ungerer <gerg@uclinux.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
	"Frederik Völkel" <frederik.voelkel@fau.de>,
	"Jiri Slaby" <jslaby@suse.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-kernel@i4.cs.fau.de, "Lukas Braun" <lukas.braun@fau.de>,
	"uClinux development list" <uclinux-dev@uclinux.org>
Subject: Re: [PATCH] serial: Remove 68328 driver
Date: Mon, 11 Jan 2016 09:57:12 -0800	[thread overview]
Message-ID: <5693ECF8.9020408@hurleysoftware.com> (raw)
In-Reply-To: <568A530F.8020807@uclinux.org>

On 01/04/2016 03:10 AM, Greg Ungerer wrote:
> On 04/01/16 20:30, One Thousand Gnomes wrote:
>> On Mon, 4 Jan 2016 15:03:50 +1000
>> Greg Ungerer <gregungerer@westnet.com.au> wrote:
>>
>>> If 68328serial.c is removed is there any point keeping the
>>> architecture support for 68328 platforms?
>>>
>>> The 68328serial.c provides pretty much the only type of console
>>> that can be used on these devices. They are largely useless
>>> without this
>>
>> Probably we should - unless someone wants to stand up and say "actually
>> I'm using this with current kernels, need it, and I'll maintain it"
>>
>> Somehow I doubt anyone is.
> 
> Yep, I suspect you are right.
> I can't even remember the last time a patch or improvement
> for 68328 came past me. Same goes for 68360 cpu/platform
> as well.

And none of it builds (and there's no build coverage in arch/m68k/configs)

Regards,
Peter Hurley

  reply	other threads:[~2016-01-11 17:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 10:36 [PATCH 0/9] Fix checkpatch errors Frederik Völkel
2015-12-11 10:36 ` [PATCH 1/9] drivers: tty: 68328serial.c: Add missing spaces(checkpatch) Frederik Völkel
2015-12-11 10:36 ` [PATCH 2/9] drivers: tty: 68328serial.c: remove unnecessary spaces(checkpatch) Frederik Völkel
2015-12-11 10:36 ` [PATCH 3/9] drivers: tty: 68328serial.c: Do not initialize statics to 0 Frederik Völkel
2015-12-11 10:36 ` [PATCH 4/9] drivers: tty: 68328serial.c: Fix "foo * bar" should be "foo *bar" Frederik Völkel
2015-12-11 10:36 ` [PATCH 5/9] drivers: tty: 68328serial.c: Remove parentheses after return Frederik Völkel
2015-12-11 10:36 ` [PATCH 6/9] drivers: tty: 68328serial.c: Use tabs for indentation Frederik Völkel
2015-12-13  7:08   ` Greg KH
2015-12-13  7:09     ` Greg KH
2015-12-11 10:36 ` [PATCH 7/9] drivers: tty: 68328serial.c: remove trailing whitespaces Frederik Völkel
2015-12-11 10:36 ` [PATCH 8/9] drivers: tty: 68328serial.c: Use use same indentation for switch/case Frederik Völkel
2015-12-11 10:36 ` [PATCH 9/9] drivers: tty: 68328serial.c: Move trailing statements to next line Frederik Völkel
2015-12-13  7:06 ` [PATCH 0/9] Fix checkpatch errors Greg KH
2015-12-13 17:44   ` Frederik
2015-12-13 18:15     ` Nicolai Stange
2015-12-13 18:26       ` Frederik
2015-12-13 20:31         ` Ken Moffat
2015-12-16 15:16 ` [PATCH v2 0/4] " Frederik Völkel
2015-12-16 15:16   ` [PATCH v2 1/4] drivers: tty: 68328serial.c: Use tabs for indentation Frederik Völkel
2015-12-16 15:43     ` One Thousand Gnomes
2015-12-16 16:25       ` Peter Hurley
2015-12-16 15:16   ` [PATCH v2 2/4] drivers: tty: 68328serial.c: remove trailing whitespaces Frederik Völkel
2015-12-16 15:17   ` [PATCH v2 3/4] drivers: tty: 68328serial.c: Use use same indentation for switch/case Frederik Völkel
2015-12-16 15:17   ` [PATCH v2 4/4] drivers: tty: 68328serial.c: Move trailing statements to next line Frederik Völkel
2015-12-18 11:28 ` [PATCH] serial: Remove 68328 driver Frederik Völkel
2015-12-18 14:27   ` Geert Uytterhoeven
2015-12-18 14:27     ` Geert Uytterhoeven
2016-01-04  5:03     ` Greg Ungerer
2016-01-04 10:30       ` One Thousand Gnomes
2016-01-04 11:10         ` Greg Ungerer
2016-01-11 17:57           ` Peter Hurley [this message]
2016-01-11 17:53   ` Peter Hurley

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=5693ECF8.9020408@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=frederik.voelkel@fau.de \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lukas.braun@fau.de \
    --cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.