From: Andrew Morton <akpm@linux-foundation.org>
To: "Vitaly Wool" <vitalywool@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: make probing for TXEN bug a config option
Date: Wed, 14 Feb 2007 10:20:56 -0800 [thread overview]
Message-ID: <20070214102056.aa024d70.akpm@linux-foundation.org> (raw)
In-Reply-To: <acd2a5930702140541n20752906ge1ff58efed460ed5@mail.gmail.com>
On Wed, 14 Feb 2007 05:41:53 -0800
"Vitaly Wool" <vitalywool@gmail.com> wrote:
> On 2/14/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Wed, 14 Feb 2007 11:37:52 +0300 "Vitaly Wool" <vitalywool@gmail.com> wrote:
> > > Hmm, why? I can't think of a platform where one 8250-compatible UART is
> > > problematic and another isn't :)
> > >
> >
> > Is it not possible that the same kernel package can be installed on systems
> > which do and don't need this feature? If so, we don't want to force the
> > provider of that package to create two packages.
> >
> > That, plus the chances of the package creator actually knowing about this
> > option aren't great.
> >
> > Generally, if it can be done at runtime it is better to do so, no?
>
> Okay, yes, I see your point. The same kernel might actually be
> supporting several machines.
>
> But having that as a config option doesn't look too attractive to me.
> What about adding a new flag to plat_serial 8250 stuff instead?
plat_serial8250_port.flags? Dunno, I'm unfamiliar with it. That seems to be how
the share_irqs option is handled.
next prev parent reply other threads:[~2007-02-14 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 16:43 [PATCH] 8250: make probing for TXEN bug a config option Vitaly Wool
2007-02-14 6:46 ` Andrew Morton
[not found] ` <acd2a5930702140037yff0b77dl2714ea7869bdde54@mail.gmail.com>
2007-02-14 8:47 ` Andrew Morton
2007-02-14 13:41 ` Vitaly Wool
2007-02-14 18:20 ` Andrew Morton [this message]
2007-03-14 21:38 ` Vitaly Wool
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=20070214102056.aa024d70.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vitalywool@gmail.com \
/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.