From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Dave Mitchell <dmitchell@amcc.com>,
arnd@arndb.de
Subject: Re: [PATCH] of_serial: Add UPF_FIXED_TYPE flag
Date: Sat, 20 Jun 2009 08:59:10 +1000 [thread overview]
Message-ID: <1245452350.16880.13.camel@pasglop> (raw)
In-Reply-To: <1245399861.10629.194.camel@concordia>
On Fri, 2009-06-19 at 18:24 +1000, Michael Ellerman wrote:
> I think we /probably/ want a similar change in legacy_serial.c, for
> soc
> ports at least.
>
> Or do people have things that are compatible "ns16550" but aren't?
>
Do we really want to keep of_serial.c ?
I fail to see the point in keeping -both- the of_serial (of_device
variant) and the legacy serial stuff which shims the device-tree into
platform devices.
They tend to clash with each other too, which is annoying.
Cheers,
Ben
prev parent reply other threads:[~2009-06-19 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 23:39 [PATCH] of_serial: Add UPF_FIXED_TYPE flag Dave Mitchell
2009-06-19 8:24 ` Michael Ellerman
2009-06-19 22:59 ` Benjamin Herrenschmidt [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=1245452350.16880.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=dmitchell@amcc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).