From: Ralf Baechle <ralf@linux-mips.org>
To: John Crispin <blogic@openwrt.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ralph Hempel <ralph.hempel@lantiq.com>,
Felix Fietkau <nbd@openwrt.org>,
linux-mips@linux-mips.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH V6] MIPS: lantiq: add serial port support
Date: Wed, 6 Apr 2011 01:58:10 +0200 [thread overview]
Message-ID: <20110405235810.GA9962@linux-mips.org> (raw)
In-Reply-To: <4D9B2054.8090305@openwrt.org>
On Tue, Apr 05, 2011 at 03:59:48PM +0200, John Crispin wrote:
> > Acked-by: Alan Cox <alan@linux.intel.com>
> >
> >
> Hi Alan,
>
> thanks alot :)
Thanks everybody; queued for 2.6.40.
Ralf
prev parent reply other threads:[~2011-04-05 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 12:10 [PATCH V6] MIPS: lantiq: add serial port support John Crispin
2011-04-05 13:55 ` Alan Cox
2011-04-05 13:59 ` John Crispin
2011-04-05 23:58 ` Ralf Baechle [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=20110405235810.GA9962@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=ralph.hempel@lantiq.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;
as well as URLs for NNTP newsgroup(s).