From: Alan Cox <alan@linux.intel.com>
To: Sonic Zhang <sonic.adi@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH 2/2] serial:blackfin: rename Blackfin serial driver to bfin_uart.c
Date: Tue, 19 Jul 2011 17:05:53 +0100 [thread overview]
Message-ID: <20110719170553.2364ef7a@bob.linux.org.uk> (raw)
In-Reply-To: <1311070165-29402-2-git-send-email-sonic.adi@gmail.com>
Looks good to me - and thanks for splitting the move and the style
changes into two patches
Acked-by: Alan Cox <alan@linux.intel.com>
next prev parent reply other threads:[~2011-07-19 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 10:09 [PATCH 1/2] serial:blackfin: Correct coding style in bfin serial driver Sonic Zhang
2011-07-19 10:09 ` [PATCH 2/2] serial:blackfin: rename Blackfin serial driver to bfin_uart.c Sonic Zhang
2011-07-19 16:05 ` Alan Cox [this message]
2011-07-19 15:28 ` [PATCH 1/2] serial:blackfin: Correct coding style in bfin serial driver Joe Perches
2011-07-20 2:44 ` Zhang, Sonic
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=20110719170553.2364ef7a@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sonic.adi@gmail.com \
--cc=sonic.zhang@analog.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).