From: Russell King <rmk@arm.linux.org.uk>
To: Matthew Wilcox <willy@debian.org>
Cc: Hu Gang <gang_hu@soul.com.cn>, linux-kernel@vger.kernel.org
Subject: Re: [patch] Serial 2/2
Date: Sun, 29 Sep 2002 18:27:07 +0100 [thread overview]
Message-ID: <20020929182706.B15924@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020929171104.G18377@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Sun, Sep 29, 2002 at 05:11:04PM +0100
On Sun, Sep 29, 2002 at 05:11:04PM +0100, Matthew Wilcox wrote:
> i'm not sure about the rest of your changes, but this one is definitely
> wrong.
I've sent Hu my proposed solution and I'm waiting to hear back.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-09-29 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 16:11 [patch] Serial 2/2 Matthew Wilcox
2002-09-29 17:27 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-29 4:17 Hu Gang
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=20020929182706.B15924@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=gang_hu@soul.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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).