From: Greg KH <gregkh@linuxfoundation.org>
To: Jun Chen <jun.d.chen@intel.com>
Cc: Alan Cox <alan@linux.intel.com>, Bi Chao <chao.bi@intel.com>,
serial <linux-serial@vger.kernel.org>,
"russ.gorby" <russ.gorby@intel.com>,
linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: [PATCH] serial: ifx6x60: ifx_spi_write don't need to do mrdy_assert when fifo is not empty.
Date: Fri, 16 Nov 2012 04:38:34 -0800 [thread overview]
Message-ID: <20121116123834.GA9327@kroah.com> (raw)
In-Reply-To: <1353064117.24092.4.camel@chenjun-workstation>
On Fri, Nov 16, 2012 at 06:08:37AM -0500, Jun Chen wrote:
>
> This patch check whether the fifo lenth is empty before writing new data to fifo.If condition
> is true,ifx_spi_write need to trigger one mrdy_assert. If condition is false,the mrdy_assert
> will be trigger by the next ifx_spi_io.
>
> Cc: Bi Chao <chao.bi@intel.com>
> Signed-off-by: Chen Jun <jun.d.chen@intel.com>
> ---
> drivers/tty/serial/ifx6x60.c | 14 +++++++++++---
> 1 files changed, 11 insertions(+), 3 deletions(-)
What tree did you make this against? It doesn't apply to my tty-next
tree at all :(
greg k-h
next prev parent reply other threads:[~2012-11-16 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 11:08 [PATCH] serial: ifx6x60: ifx_spi_write don't need to do mrdy_assert when fifo is not empty Jun Chen
2012-11-16 12:38 ` Greg KH [this message]
2012-11-18 3:14 ` Chen, Jun D
2012-11-18 3:30 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-11-19 10:07 Jun Chen
2012-11-07 17:04 Jun Chen
2012-11-07 9:11 ` Alan Cox
2012-11-06 9:28 Jun Chen
2012-11-06 9:47 ` Alan Cox
2012-11-07 9:09 ` Chen, Jun D
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=20121116123834.GA9327@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=chao.bi@intel.com \
--cc=fengguang.wu@intel.com \
--cc=jun.d.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=russ.gorby@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.