All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] sysfs: Introduce sysfs_{un,}break_active_protection()
Date: Wed, 1 Aug 2018 08:53:54 -0700	[thread overview]
Message-ID: <20180801155354.GQ1206094@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20180730184052.13442-2-bart.vanassche@wdc.com>

On Mon, Jul 30, 2018 at 11:40:51AM -0700, Bart Van Assche wrote:
> Introduce these two functions and export them such that the next patch
> can add calls to these functions from the SCSI core.
> 
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: <stable@vger.kernel.org>

Acked-by: Tejun Heo <tj@kernel.org>

Thanks.

-- 
tejun

  reply	other threads:[~2018-08-01 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180730184052.13442-1-bart.vanassche@wdc.com>
2018-07-30 18:40 ` [PATCH 1/2] sysfs: Introduce sysfs_{un,}break_active_protection() Bart Van Assche
2018-08-01 15:53   ` Tejun Heo [this message]
2018-08-02  8:31   ` Greg Kroah-Hartman
2018-07-30 18:40 ` [PATCH 2/2] Avoid that SCSI device removal through sysfs triggers a deadlock Bart Van Assche
2018-08-01 15:54   ` Tejun Heo
2018-08-01 21:16   ` Bart Van Assche
2018-08-01 22:58     ` Bart Van Assche
2018-08-02 17:47       ` Bart Van Assche
     [not found] <20180802175141.8699-1-bart.vanassche@wdc.com>
2018-08-02 17:51 ` [PATCH 1/2] sysfs: Introduce sysfs_{un,}break_active_protection() Bart Van Assche

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=20180801155354.GQ1206094@devbig004.ftw2.facebook.com \
    --to=tj@kernel.org \
    --cc=bart.vanassche@wdc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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.