From: Greg KH <greg@kroah.com>
To: Yin Kangkai <kangkai.yin@linux.intel.com>
Cc: linux-serial <linux-serial@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
"Woodhouse, David" <david.woodhouse@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: also set the uartclk value in resume after goes to highspeed
Date: Thu, 3 Feb 2011 14:15:00 -0800 [thread overview]
Message-ID: <20110203221500.GA3979@kroah.com> (raw)
In-Reply-To: <20110125074447.GJ3315@kai-debian>
On Tue, Jan 25, 2011 at 03:44:47PM +0800, Yin Kangkai wrote:
> From: Yin Kangkai <kangkai.yin@intel.com>
Please don't include the git patch in the email, use git-send-email to
send it out.
Anyway, this doesn't apply to the latest linux-next tree, care to
refresh it and resend it?
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-03 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 7:44 [PATCH] serial: also set the uartclk value in resume after goes to highspeed Yin Kangkai
2011-02-03 22:15 ` Greg KH [this message]
2011-02-09 3:34 ` [PATCH resend 1/2] " Yin Kangkai
2011-02-09 3:35 ` [PATCH resend 2/2] serial: change the divisor latch only when prescalar actually changed Yin Kangkai
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=20110203221500.GA3979@kroah.com \
--to=greg@kroah.com \
--cc=david.woodhouse@intel.com \
--cc=gregkh@suse.de \
--cc=kangkai.yin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).