public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bean Huo <huobean@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-scsi@vger.kernel.org, Avri Altman <avri.altman@wdc.com>,
	Bean Huo <beanhuo@micron.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Keoseong Park <keosung.park@samsung.com>
Subject: Re: [PATCH] scsi: ufs: Split the drivers/scsi/ufs directory
Date: Thu, 19 May 2022 11:07:13 +0200	[thread overview]
Message-ID: <0a6abfbcdadccf6a47fbdd8393d769429fa54d7a.camel@gmail.com> (raw)
In-Reply-To: <20220511212552.655341-1-bvanassche@acm.org>

On Wed, 2022-05-11 at 14:25 -0700, Bart Van Assche wrote:
> Split the drivers/scsi/ufs directory into 'core' and 'host'
> directories
> under the drivers/ufs/ directory. Move shared header files into the
> include/ufs/ directory. This separation makes it clear which header
> files UFS drivers are allowed to include (include/ufs/*.h) and which
> header files UFS drivers are not allowed to include
> (drivers/ufs/core/*.h).
> 
> Update the MAINTAINERS file. Add myself as a UFS reviewer.
> 
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Avri Altman <avri.altman@wdc.com>
> Cc: Bean Huo <beanhuo@micron.com>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Keoseong Park <keosung.park@samsung.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>

Tested-by: Bean Huo <beanhuo@micron.com>
Reviewed-by: Bean Huo <beanhuo@micron.com>


  parent reply	other threads:[~2022-05-19  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 21:25 [PATCH] scsi: ufs: Split the drivers/scsi/ufs directory Bart Van Assche
     [not found] ` <202205122323.RcDb4pBm-lkp@intel.com>
2022-05-12 17:18   ` Bart Van Assche
2022-05-18 18:33 ` Avri Altman
2022-05-19  9:07 ` Bean Huo [this message]
2022-05-19 12:09 ` Adrian Hunter
2022-05-20  0:28 ` Martin K. Petersen
2022-05-24  3:27 ` Martin K. Petersen

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=0a6abfbcdadccf6a47fbdd8393d769429fa54d7a.camel@gmail.com \
    --to=huobean@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=bvanassche@acm.org \
    --cc=jaegeuk@kernel.org \
    --cc=keosung.park@samsung.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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