From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peng Tao <bergwolf@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH 1/2] staging/lustre/ptlrpc: fix ptlrpc_stop_pinger logic
Date: Mon, 25 Nov 2013 12:37:55 -0800 [thread overview]
Message-ID: <20131125203755.GA14140@kroah.com> (raw)
In-Reply-To: <1385044966-3572-1-git-send-email-bergwolf@gmail.com>
On Thu, Nov 21, 2013 at 10:42:45PM +0800, Peng Tao wrote:
> It was introduced due to a patch hunk when porting
> commit 20802057 (staging/lustre/ptlrpc: race in pinger).
This patch was in 3.12, so this needs to go to the stable tree for 3.12,
right? It also needs to get into 3.13-final, so please tell me that
next time so I know where to apply it to.
thanks,
greg k-h
next prev parent reply other threads:[~2013-11-25 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 14:42 [PATCH 1/2] staging/lustre/ptlrpc: fix ptlrpc_stop_pinger logic Peng Tao
2013-11-21 14:42 ` [PATCH 2/2] staging/lustre/obdclass: add empty tailing member to ctl_table Peng Tao
2013-11-25 20:37 ` Greg Kroah-Hartman [this message]
2013-11-26 1:26 ` [PATCH 1/2] staging/lustre/ptlrpc: fix ptlrpc_stop_pinger logic Peng Tao
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=20131125203755.GA14140@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=linux-kernel@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