From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, Chris Dearman <chris@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: ser-unix.c: Add hardware flow control support
Date: Mon, 21 May 2007 12:50:00 -0000 [thread overview]
Message-ID: <20070521125013.GA32273@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705211303420.27238@perivale.mips.com>
On Mon, May 21, 2007 at 01:21:51PM +0100, Maciej W. Rozycki wrote:
> On Wed, 2 May 2007, Maciej W. Rozycki wrote:
>
> > > I noticed while looking for the right place to put the option that we
> > > have an empty "set serial". Perhaps it should go under that instead.
> > > No strong preference.
> >
> > Well, we have "set remotebaud", which is at the top-level as well. And
> > which actually raises a question as to whether "set remoteflow" should not
> > be handled through "struct serial_ops" too? This way other serial
> > interfaces would have a chance to handle the option as well if somebody
> > cared.
> >
> > Any opinions?
>
> OK, I gather there is no potential interest in platform-independent
> approach at the moment, so I guess it may be implemented based on
> ser-unix.c if a need arises. Here is my current version of the patch.
This is fine with me; Eli, are the documentation changes OK?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-21 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 11:55 Maciej W. Rozycki
2007-03-30 12:08 ` Daniel Jacobowitz
2007-05-02 14:11 ` Maciej W. Rozycki
2007-05-21 12:22 ` Maciej W. Rozycki
2007-05-21 12:50 ` Daniel Jacobowitz [this message]
2007-05-21 20:08 ` Eli Zaretskii
2007-05-22 10:57 ` Maciej W. Rozycki
2007-03-30 12:26 ` Eli Zaretskii
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=20070521125013.GA32273@caradoc.them.org \
--to=drow@false.org \
--cc=chris@mips.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox