All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: Greg-KH <gregkh@linuxfoundation.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: target-devel <target-devel@vger.kernel.org>,
	stable <stable@vger.kernel.org>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH-3.18.y 2/2] iscsi-target: Fix iscsi_np reset hung task during parallel delete
Date: Thu, 16 Nov 2017 18:35:32 +0000	[thread overview]
Message-ID: <5A0DDA74.3060102@redhat.com> (raw)
In-Reply-To: <20171116164642.GI24442@kroah.com>

On 11/16/2017 10:46 AM, Greg-KH wrote:
> 
> What is the git commit id of this patch in Linus's tree?
> 

It's 978d13d60c34818a41fc35962602bdfa5c03f214


WARNING: multiple messages have this Message-ID (diff)
From: Mike Christie <mchristi@redhat.com>
To: Greg-KH <gregkh@linuxfoundation.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: target-devel <target-devel@vger.kernel.org>,
	stable <stable@vger.kernel.org>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH-3.18.y 2/2] iscsi-target: Fix iscsi_np reset hung task during parallel delete
Date: Thu, 16 Nov 2017 12:35:32 -0600	[thread overview]
Message-ID: <5A0DDA74.3060102@redhat.com> (raw)
In-Reply-To: <20171116164642.GI24442@kroah.com>

On 11/16/2017 10:46 AM, Greg-KH wrote:
> 
> What is the git commit id of this patch in Linus's tree?
> 

It's 978d13d60c34818a41fc35962602bdfa5c03f214

  reply	other threads:[~2017-11-16 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  6:17 [PATCH-3.18.y 0/2] target: stable backports Nicholas A. Bellinger
2017-11-16  6:17 ` [PATCH-3.18.y 1/2] target/iscsi: Fix iSCSI task reassignment handling Nicholas A. Bellinger
2017-11-16  6:17 ` [PATCH-3.18.y 2/2] iscsi-target: Fix iscsi_np reset hung task during parallel delete Nicholas A. Bellinger
2017-11-16  6:17   ` Nicholas A. Bellinger
2017-11-16 16:46   ` Greg-KH
2017-11-16 16:46     ` Greg-KH
2017-11-16 18:35     ` Mike Christie [this message]
2017-11-16 18:35       ` Mike Christie
2017-11-19 10:23       ` Greg-KH
2017-11-19 10:23         ` Greg-KH
2018-01-12 23:49 ` [PATCH-3.18.y 0/2] target: stable backports Nicholas A. Bellinger
2018-01-13  0:03   ` Nicholas A. Bellinger
2018-01-12 23:49   ` [PATCH-3.18.y 1/2] iscsi-target: Make TASK_REASSIGN use proper se_cmd->cmd_kref Nicholas A. Bellinger
2018-01-13  0:03     ` Nicholas A. Bellinger
2018-01-12 23:49   ` [PATCH-3.18.y 2/2] target: Avoid early CMD_T_PRE_EXECUTE failures during ABORT_TASK Nicholas A. Bellinger
2018-01-13  0:03     ` Nicholas A. Bellinger
2018-01-13 17:33   ` [PATCH-3.18.y 0/2] target: stable backports Greg-KH
2018-01-13 17:33     ` Greg-KH

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=5A0DDA74.3060102@redhat.com \
    --to=mchristi@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.de \
    --cc=nab@linux-iscsi.org \
    --cc=stable@vger.kernel.org \
    --cc=target-devel@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.