linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bean Huo <beanhuo@iokpp.de>,
	alim.akhtar@samsung.com, avri.altman@wdc.com,
	asutoshd@codeaurora.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com, stanley.chu@mediatek.com,
	beanhuo@micron.com, tomas.winkler@intel.com, cang@codeaurora.org,
	daejun7.park@samsung.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] scsi: ufs: core: Remove unnecessary if statement
Date: Fri, 14 Oct 2022 13:41:59 -0700	[thread overview]
Message-ID: <ffc4250d-7446-40eb-9218-6925f44a69ff@acm.org> (raw)
In-Reply-To: <d06a264c4544a23ccccd016c6797d889db526b64.camel@iokpp.de>

On 10/14/22 12:20, Bean Huo wrote:
> I am working on the Advanced RPMB, and trying to seperate normal unit
> descriptor and RPMB unit descriptor, will let you know if it is
> possible. or if you know the solution, please let me know, thanks.

Hi Bean,

How about setting .is_visible member of struct attribute_group in the UFS
driver and letting that callback decide which sysfs attributes are visible
depending on the logical unit type?

Thanks,

Bart.

  reply	other threads:[~2022-10-14 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  9:29 [PATCH v2 0/2] Changes for ufshcd.c Bean Huo
2022-10-10  9:29 ` [PATCH v2 1/2] scsi: ufs: core: Remove unnecessary if statement Bean Huo
2022-10-11  2:21   ` Daejun Park
2022-10-11  9:39     ` Bean Huo
2022-10-14  0:19   ` Daejun Park
2022-10-14 18:37   ` Bart Van Assche
2022-10-14 19:20     ` Bean Huo
2022-10-14 20:41       ` Bart Van Assche [this message]
2022-10-14 20:57         ` Bean Huo
2022-10-14 20:30     ` Bean Huo
2022-10-14 20:45       ` Bart Van Assche
2022-10-10  9:29 ` [PATCH v2 2/2] scsi: ufs: core: Cleanup ufshcd_slave_alloc() Bean Huo
2022-10-14 21:05   ` Bart Van Assche
2022-10-17 16:56     ` Bean Huo

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=ffc4250d-7446-40eb-9218-6925f44a69ff@acm.org \
    --to=bvanassche@acm.org \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@iokpp.de \
    --cc=beanhuo@micron.com \
    --cc=cang@codeaurora.org \
    --cc=daejun7.park@samsung.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.com \
    --cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).