linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: imx: protect Soft Reset of port with lock
Date: Mon, 13 Apr 2015 09:20:24 +0200	[thread overview]
Message-ID: <20150413072024.GA4473@kroah.com> (raw)
In-Reply-To: <552B6791.60905@mentor.com>

On Mon, Apr 13, 2015 at 03:52:01PM +0900, jiwang wrote:
> Hi Greg
> 
> On 03/27/2015 07:01 AM, Greg KH wrote:
> >On Fri, Mar 13, 2015 at 03:38:11PM +0900, Jiada Wang wrote:
> >>Previously Soft Reset (clear of SRST bit in UCR2 register)
> >>of UART in startup is not protected by lock, which may have race
> >>with console_write, as console_write may occur at anytime even
> >>when UART port is shutdown.
> >>
> >>To avoid this race, protect Soft reset of UART port with spin_lock.
> >>
> >>Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
> >>---
> >>  drivers/tty/serial/imx.c | 12 ++++++------
> >>  1 file changed, 6 insertions(+), 6 deletions(-)
> >Doesn't apply to my tree :(
> Can you tell me which tree are you using?
> so that I can submit another patch based same tree.

Always either work off of linux-next, or my tty tree, and the tty-next
branch of it on git.kernel.org.

What tree were you working against, Linus's?  If so, please read
Documentation/development_process to get an understanding of how the
kernel development process works.

thanks,

greg k-h

      reply	other threads:[~2015-04-13  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  6:38 [PATCH] serial: imx: protect Soft Reset of port with lock Jiada Wang
2015-03-26 22:01 ` Greg KH
2015-04-13  6:52   ` jiwang
2015-04-13  7:20     ` Greg KH [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=20150413072024.GA4473@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.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).