From: Kamal Mostafa <kamal@canonical.com>
To: Chris J Arges <chris.j.arges@canonical.com>
Cc: stable@vger.kernel.org, kamal.mostafa@canonical.com
Subject: Re: commit 27f344eb15dd0da80ebec80c7245e8c85043f841
Date: Wed, 01 Jul 2015 12:30:43 -0700 [thread overview]
Message-ID: <1435779043.7459.2.camel@fourier> (raw)
In-Reply-To: <20150625162200.GA5867@canonical.com>
On Thu, 2015-06-25 at 11:22 -0500, Chris J Arges wrote:
> Please consider adding commit 27f344eb15dd0da80ebec80c7245e8c85043f841 to the
> following stable trees: 3.10.y 3.12.y 3.13.y-ckt 3.14.y
>
> It is a clean cherry-pick for these series, and addresses an issue on Power
> systems under I/O stress and using the lpfc driver.
>
> BugLink: http://bugs.launchpad.net/bugs/1468416
>
> --
>
> From 27f344eb15dd0da80ebec80c7245e8c85043f841 Mon Sep 17 00:00:00 2001
> From: James Smart <james.smart@emulex.com>
> Date: Wed, 7 May 2014 17:16:46 -0400
> Subject: [PATCH] lpfc: Add iotag memory barrier
Thanks Chris! Queued for 3.13-stable.
-Kamal
prev parent reply other threads:[~2015-07-01 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 16:22 commit 27f344eb15dd0da80ebec80c7245e8c85043f841 Chris J Arges
2015-06-27 0:49 ` Greg KH
2015-06-29 13:33 ` Jiri Slaby
2015-07-01 19:30 ` 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=1435779043.7459.2.camel@fourier \
--to=kamal@canonical.com \
--cc=chris.j.arges@canonical.com \
--cc=kamal.mostafa@canonical.com \
--cc=stable@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).