linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Sayali Lokhande <sayalil@codeaurora.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	subhashj@codeaurora.org, cang@codeaurora.org,
	vivek.gautam@codeaurora.org, rnayak@codeaurora.org,
	vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
	martin.petersen@oracle.com, asutoshd@codeaurora.org,
	evgreen@chromium.org, riteshh@codeaurora.org,
	linux-scsi@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V5 2/2] scsi: ufs: Add configfs support for ufs provisioning
Date: Tue, 17 Jul 2018 05:48:05 -0700	[thread overview]
Message-ID: <20180717124805.GB22099@infradead.org> (raw)
In-Reply-To: <4964583a-d13f-7b92-9838-e4398ec8c682@codeaurora.org>

On Wed, Jul 11, 2018 at 03:20:06PM +0530, Sayali Lokhande wrote:
> Agree. Will add separate config for UFS Provision and set it dependent on
> CONFIGFS_FS

Please add an actual CONFIG_UFS_PROVISIONING user selectable option.

  reply	other threads:[~2018-07-17 12:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1530858040-13971-1-git-send-email-sayalil@codeaurora.org>
2018-07-06  6:20 ` [PATCH V5 1/2] scsi: ufs: set the device reference clock setting Sayali Lokhande
2018-07-06 21:07   ` Rob Herring
2018-07-16  8:28     ` Sayali Lokhande
2018-07-06  6:20 ` [PATCH V5 2/2] scsi: ufs: Add configfs support for ufs provisioning Sayali Lokhande
2018-07-08 20:21   ` Christoph Hellwig
2018-07-11  9:50     ` Sayali Lokhande
2018-07-17 12:48       ` Christoph Hellwig [this message]
2018-07-09 17:48   ` Evan Green
2018-07-16  8:10     ` Sayali Lokhande
2018-07-16 23:46       ` Evan Green
2018-07-17  0:04         ` Bart Van Assche
2018-07-17 20:23           ` Evan Green
2018-07-17 21:06             ` Bart Van Assche
2018-07-18  8:56               ` gregkh
2018-07-18 17:30                 ` Bart Van Assche
2018-07-18 17:45                   ` gregkh
2018-07-30  7:46             ` Sayali Lokhande
2018-07-30 23:39               ` Evan Green
2018-07-31  5:18                 ` Sayali Lokhande

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=20180717124805.GB22099@infradead.org \
    --to=hch@infradead.org \
    --cc=asutoshd@codeaurora.org \
    --cc=cang@codeaurora.org \
    --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=riteshh@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=sayalil@codeaurora.org \
    --cc=subhashj@codeaurora.org \
    --cc=vinholikatti@gmail.com \
    --cc=vivek.gautam@codeaurora.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;
as well as URLs for NNTP newsgroup(s).