From: Kamal Mostafa <kamal@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: kamal.mostafa@canonical.com, tatsu@ab.jp.nec.com,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/1][3.13.y-ckt] tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
Date: Fri, 11 Dec 2015 11:00:52 -0800 [thread overview]
Message-ID: <1449860452.28274.0.camel@fourier> (raw)
In-Reply-To: <cover.1449611752.git.joseph.salisbury@canonical.com>
On Tue, 2015-12-08 at 17:11 -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider including upstream commit e81107d4c6bd098878af9796b24edc8d4a9524fd
> in the next v3.13.y-ckt release. This commit was included mainline as of v4.3-rc5.
> It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1512815 .
>
> commit e81107d4c6bd098878af9796b24edc8d4a9524fd
> Author: Kosuke Tatsukawa <tatsu@ab.jp.nec.com>
> Date: Fri Oct 2 08:27:05 2015 +0000
>
> tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
>
> Commit e81107d4 does not apply cleanly to v3.13.y-ckt, so I performed a backport, which is
> in email 1/1.
Thanks very much Joseph. Queued for 3.13-stable.
-Kamal
>
> Sincerely,
>
> Joseph Salisbury
>
>
>
>
> Kosuke Tatsukawa (1):
> tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
>
> drivers/tty/n_tty.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
prev parent reply other threads:[~2015-12-11 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 22:11 [PATCH 0/1][3.13.y-ckt] tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c Joseph Salisbury
2015-12-08 22:11 ` [PATCH 1/1][3.13.y-ckt] " Joseph Salisbury
2015-12-11 19:00 ` Kamal Mostafa [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=1449860452.28274.0.camel@fourier \
--to=kamal@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=joseph.salisbury@canonical.com \
--cc=jslaby@suse.com \
--cc=kamal.mostafa@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tatsu@ab.jp.nec.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