From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: SCC3 UART for MPC850
Date: Tue, 04 Mar 2003 01:03:30 +0100 [thread overview]
Message-ID: <20030304000335.13A00C6E0C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 03 Mar 2003 16:46:18 MST." <20030303234618.GA12721@ip68-0-152-218.tc.ph.cox.net>
In message <20030303234618.GA12721@ip68-0-152-218.tc.ph.cox.net> you wrote:
>
> > Sorry, this is one of our patches that never was accepted for the
> > official source trees (also including hardware flow control).
>
> ... because you never split things out into logical chunks which make
> life easier on people trying to understand what changed and why. Our
> last merge went well I thought, and I'm up for another round if you are.
It would be too much trouble to separate the hardware flow control
stuff from the other port configuration options. I feel it should be
sufficient to have a set of changes local to one single source file.
You say it is not sufficent. OK. You are the maintainer, I ain't.
It's your decision, and I won't discuss it.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Most people would like to be delivered from temptation but would
like it to keep in touch." - Robert Orben
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-03-04 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030303234618.GA12721@ip68-0-152-218.tc.ph.cox.net>
2003-03-04 0:03 ` Wolfgang Denk [this message]
2003-03-04 18:28 ` SCC3 UART for MPC850 Tom Rini
2003-03-03 14:16 Steven Blakeslee
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 13:52 Donald MacArthur
2003-03-03 14:11 ` Wolfgang Denk
2003-03-03 22:25 ` Dan Malek
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=20030304000335.13A00C6E0C@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).