mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Evan Green <evgreen@chromium.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>,
	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Stanislav Nijnikov <stanislav.nijnikov@wdc.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bart.VanAssche@wdc.com
Subject: Re: [PATCH v4] scsi: ufs: Make sysfs attributes writable
Date: Tue, 4 Sep 2018 13:27:26 +0300	[thread overview]
Message-ID: <8fd05b2d-fa48-78af-6f1c-7e485c1008f6@intel.com> (raw)
In-Reply-To: <6dd8a547-7260-09b8-9096-8a1564b08e70@intel.com>

On 22/08/18 14:00, Adrian Hunter wrote:
> On 09/08/18 01:44, Evan Green wrote:
>> This change makes the UFS controller's sysfs attributes writable, which
>> will enable users to provision unprovisioned UFS devices, or
>> re-provision unlocked UFS devices.
>>
>> Signed-off-by: Evan Green <evgreen@chromium.org>
> 
> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> 

This patch has my Ack and Reviewed-by: Stanislav Nijnikov, so can it be
queued for v4.20?  There is also Evan's "[PATCH] scsi: ufs: Make sysfs flags
writable"

  reply	other threads:[~2018-09-04 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 22:44 Evan Green
2018-08-09  8:14 ` Stanislav Nijnikov
2018-08-22 11:00 ` Adrian Hunter
2018-09-04 10:27   ` Adrian Hunter [this message]
2018-09-25 18:40     ` Doug Anderson
2018-09-26  1:08       ` Martin K. Petersen
2018-09-26  1:46         ` Doug Anderson
2018-09-26 17:41           ` Evan Green
2018-09-27  6:32             ` Avri Altman
2018-09-27 14:01               ` Christoph Hellwig
2018-09-27 23:16                 ` Evan Green

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=8fd05b2d-fa48-78af-6f1c-7e485c1008f6@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=evgreen@chromium.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanislav.nijnikov@wdc.com \
    --cc=vinholikatti@gmail.com \
    /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

all inboxes | Powered by JetHome®