From: Bart Van Assche <bvanassche@acm.org>
To: Himanshu Batra <himanshubatra@google.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, vamshigajjela@google.com,
manugautam@google.com
Subject: Re: [PATCH v3] scsi: ufs: sysfs: Add HS_GEAR6 string in power_info/gear sysfs output
Date: Tue, 16 Jun 2026 06:37:43 -0700 [thread overview]
Message-ID: <c040d167-8747-43f7-ac30-2f5c5bcfbc02@acm.org> (raw)
In-Reply-To: <20260616100121.548759-1-himanshubatra@google.com>
On 6/16/26 3:01 AM, Himanshu Batra wrote:
> In power_info/gear sysfs, currently it supports output only till gear 5.
> If operating mode is gear 6, it outputs "UNKNOWN".
> Add support for HS_GEAR6 string in sysfs output when operating mode
> is gear 6.
Some general advice:
- New versions of a patch should be posted as a new email thread instead
of as a reply to an existing email conversation. Replies to an
existing email conversation tend to get overlooked.
- At least 24 hours should elapse before a new version of a patch is
posted. Otherwise reviewers who are in another time zone don't have
the chance to reply. For large patch series, more time should elapse
between reposts (e.g. one week).
- The "scsi:" prefix is no longer used for UFS kernel patches.
Since the code changes look good to me:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-06-16 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 14:26 [PATCH] ufs: " himanshubatra
2026-06-16 4:22 ` VAMSHI GAJJELA
2026-06-16 8:27 ` Himanshu Batra
2026-06-16 8:31 ` [PATCH v2] scsi: ufs: sysfs: " himanshubatra
2026-06-16 9:44 ` Greg KH
2026-06-16 10:01 ` [PATCH v3] " Himanshu Batra
2026-06-16 13:37 ` Bart Van Assche [this message]
2026-06-18 3:05 ` Himanshu Batra
2026-07-12 17:37 ` 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=c040d167-8747-43f7-ac30-2f5c5bcfbc02@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=himanshubatra@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=manugautam@google.com \
--cc=martin.petersen@oracle.com \
--cc=vamshigajjela@google.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
Powered by JetHome