From: Paul Bolle <pebolle@tiscali.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] m68k: Remove references to obsolete CONFIG_SERIAL167
Date: Thu, 17 Nov 2011 20:53:56 +0100 [thread overview]
Message-ID: <1321559636.20271.287.camel@x61.thuisdomein> (raw)
In-Reply-To: <CAMuHMdXsHgUd_oggpKoS2t6Tm8MnEjLnWmi4Hswz_nQjSWsozA@mail.gmail.com>
On Thu, 2011-11-17 at 20:33 +0100, Geert Uytterhoeven wrote:
> On Sun, Nov 13, 2011 at 12:02, Paul Bolle <pebolle@tiscali.nl> wrote:
> > 1) I've been looking at this impressive dependency list a few days back.
> > My impression was that it can be reduced to only AMIGA_BUILTIN_SERIAL=y.
> > (After that this Kconfig symbol might better be renamed to
> > AMIGA_BUILTIN_SERIAL_CONSOLE.)
> >
> > I might have a draft patch to drop the dependencies somewhere. I need to
> > have another look at that (draft) patch before I can submit it.
>
> You are right: all drivers (except for AMIGA_BUILTIN_SERIAL) got lost due to
> bitrot, or never made it to mainline. Will fix.
Nice.
> But please keep SERIAL_CONSOLE.
Why do you care about SERIAL_CONSOLE? If it's only really used by
AMIGA_BUILTIN_SERIAL why shouldn't we rename it to
AMIGA_BUILTIN_SERIAL_CONSOLE?
> BTW, updating the m68k defconfigs is also on my list.
Nice too. Jiri Kosina already claimed to be able to handle any problems
caused by my cleaning efforts (which I haven't made public, since I'm
still pondering on a way to publish a 400K+ patch).
Paul Bolle
next prev parent reply other threads:[~2011-11-17 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 10:31 [PATCH] m68k: Remove references to obsolete CONFIG_SERIAL167 Geert Uytterhoeven
2011-11-13 11:02 ` Paul Bolle
2011-11-17 19:33 ` Geert Uytterhoeven
2011-11-17 19:53 ` Paul Bolle [this message]
2011-11-17 21:05 ` Geert Uytterhoeven
2011-11-17 21:34 ` Paul Bolle
2011-11-17 21:40 ` Paul Bolle
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=1321559636.20271.287.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=trivial@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