mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nitin Rawat <quic_nitirawa@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>, <mani@kernel.org>,
	<James.Bottomley@HansenPartnership.com>,
	<martin.petersen@oracle.com>, <bvanassche@acm.org>,
	<avri.altman@wdc.com>, <ebiggers@google.com>,
	<neil.armstrong@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH V4 2/3] scsi: ufs: core: Add ufshcd_dme_rmw to modify DME attributes
Date: Thu, 10 Jul 2025 21:30:17 +0530	[thread overview]
Message-ID: <9d47157e-955e-4694-b2fe-b0d6a685afef@quicinc.com> (raw)
In-Reply-To: <cc6e8ae1-d63a-4f90-8752-07251b3bff04@oss.qualcomm.com>



On 7/10/2025 5:56 PM, Konrad Dybcio wrote:
> On 7/9/25 10:56 PM, Nitin Rawat wrote:
>> Introduce `ufshcd_dme_rmw` API to read, modify, and write DME
>> attributes in UFS host controllers using a mask and value.
>>
>> Reported-by: kernel test robot <lkp@intel.com>
> 
> This tag makes sense if your patch is merged into the tree
> but happens to contain a build warning/error. Using it here
> makes it look like the kernel test robot suggested
> introducing this wrapper

sure Konrad. Thanks. I'll update in next patchset.

> 
> Konrad


  reply	other threads:[~2025-07-10 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 20:56 [PATCH V4 0/3] ufs: ufs-qcom: Align programming sequence as per HW spec Nitin Rawat
2025-07-09 20:56 ` [PATCH V4 1/3] ufs: ufs-qcom: Update esi_vec_mask for HW major version >= 6 Nitin Rawat
2025-07-09 20:56 ` [PATCH V4 2/3] scsi: ufs: core: Add ufshcd_dme_rmw to modify DME attributes Nitin Rawat
2025-07-10 12:26   ` Konrad Dybcio
2025-07-10 16:00     ` Nitin Rawat [this message]
2025-07-09 20:56 ` [PATCH V4 3/3] ufs: ufs-qcom: Enable QUnipro Internal Clock Gating Nitin Rawat

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=9d47157e-955e-4694-b2fe-b0d6a685afef@quicinc.com \
    --to=quic_nitirawa@quicinc.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=ebiggers@google.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mani@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=neil.armstrong@linaro.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

all inboxes | Powered by JetHome®