From: Kamal Mostafa <kamal@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Kamal Mostafa <kamal.mostafa@canonical.com>,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, roland@purestorage.com,
ogerlitz@mellanox.com, erezsh@mellanox.com,
alex.estrin@intel.com, linux-rdma@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
kamalh@mellanox.com
Subject: Re: [PATCH][v3.19.y-ckt] IB/ipoib: change init sequence ordering
Date: Thu, 02 Jul 2015 10:16:09 -0700 [thread overview]
Message-ID: <1435857369.23145.2.camel@fourier> (raw)
In-Reply-To: <55942302.10602@canonical.com>
On Wed, 2015-07-01 at 13:27 -0400, Joseph Salisbury wrote:
> Hello,
>
> Please consider including upstream commits
> be7aa663fc1d9156798f5af3c60e6df45e1fe5de and
> e135106fac9525352feb8e49077c8f46c3eaf288 in the next v3.19.y-ckt
> release. They were included mainline as of v4.1-rc1. These commits
> have been tested and confirmed to resolve
> http://bugs.launchpad.net/bugs/1467912 .
>
>
> commit be7aa663fc1d9156798f5af3c60e6df45e1fe5de
> Author: Doug Ledford <dledford@redhat.com>
> Date: Sat Feb 21 19:27:00 2015 -0500
>
> IB/ipoib: change init sequence ordering
>
> commit e135106fac9525352feb8e49077c8f46c3eaf288
> Author: Doug Ledford <dledford@redhat.com>
> Date: Sat Feb 21 19:26:59 2015 -0500
>
> IB/ipoib: factor out ah flushing
>
> The bug reporter states this bug is only happening with the 3.19 kernel,
> these commits may not be needed in other stable kernels.
Queued up for 3.19-stable.
And thanks very much for the extra analysis and ack on this, Doug.
-Kamal
prev parent reply other threads:[~2015-07-02 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 17:27 [PATCH][v3.19.y-ckt] IB/ipoib: change init sequence ordering Joseph Salisbury
2015-07-01 17:27 ` Joseph Salisbury
2015-07-01 17:42 ` Doug Ledford
2015-07-02 17:16 ` 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=1435857369.23145.2.camel@fourier \
--to=kamal@canonical.com \
--cc=alex.estrin@intel.com \
--cc=dledford@redhat.com \
--cc=erezsh@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=joseph.salisbury@canonical.com \
--cc=kamal.mostafa@canonical.com \
--cc=kamalh@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@purestorage.com \
--cc=sean.hefty@intel.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 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.