From: Greg Ungerer <gerg@uclinux.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.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, 4 Jan 2016 21:10:07 +1000 [thread overview]
Message-ID: <568A530F.8020807@uclinux.org> (raw)
In-Reply-To: <20160104103031.655b6f61@lxorguk.ukuu.org.uk>
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.
Regards
Greg
next prev parent reply other threads:[~2016-01-04 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1449830170-15096-1-git-send-email-frederik.voelkel@fau.de>
[not found] ` <1450438103-1059-1-git-send-email-frederik.voelkel@fau.de>
2015-12-18 14:27 ` [PATCH] serial: Remove 68328 driver Geert Uytterhoeven
2016-01-04 5:03 ` Greg Ungerer
2016-01-04 10:30 ` One Thousand Gnomes
2016-01-04 11:10 ` Greg Ungerer [this message]
2016-01-11 17:57 ` Peter Hurley
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=568A530F.8020807@uclinux.org \
--to=gerg@uclinux.org \
--cc=frederik.voelkel@fau.de \
--cc=geert@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox