From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Jihed Chaibi" <jihed.chaibi.dev@gmail.com>,
<heikki.krogerus@linux.intel.com>, <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linux.dev>,
<skhan@linuxfoundation.org>
Subject: Re: [PATCH 1/1] usb: typec: tipd: fix typo in TPS_STATUS_HIGH_VOLAGE_WARNING macro
Date: Thu, 22 May 2025 01:47:54 -0600 [thread overview]
Message-ID: <DA2IV4ZGT2M8.3QXO3L57VXSA5@brighamcampbell.com> (raw)
In-Reply-To: <20250521214851.386796-1-jihed.chaibi.dev@gmail.com>
On Wed May 21, 2025 at 3:48 PM MDT, Jihed Chaibi wrote:
> "VOLAGE" should become "VOLTAGE"
>
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
Nice work! I was able to successfully compile this driver with your
changes and I don't see any further references to the misspelled macro.
Patches which fix issues which were introduced in some previous commit
typically indicate the offending commit via the "Fixes" tag. Admittedly,
I don't know if the tag is reserved for technical bugs rather than typos
such as the one you addressed, but such a tag would look like the
following for this patch:
Fixes: e011178579b57c03 ("usb: typec: tipd: fix typo in TPS_STATUS_HIGH_VOLAGE_WARNING macro")
> ---
> drivers/usb/typec/tipd/tps6598x.h | 2 +-
> drivers/usb/typec/tipd/trace.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/typec/tipd/tps6598x.h b/drivers/usb/typec/tipd/tps6598x.h
> index 9b23e9017..cecb8d11d 100644
> --- a/drivers/usb/typec/tipd/tps6598x.h
> +++ b/drivers/usb/typec/tipd/tps6598x.h
> @@ -27,7 +27,7 @@
> #define TPS_STATUS_OVERCURRENT BIT(16)
> #define TPS_STATUS_GOTO_MIN_ACTIVE BIT(26)
> #define TPS_STATUS_BIST BIT(27)
> -#define TPS_STATUS_HIGH_VOLAGE_WARNING BIT(28)
> +#define TPS_STATUS_HIGH_VOLTAGE_WARNING BIT(28)
> #define TPS_STATUS_HIGH_LOW_VOLTAGE_WARNING BIT(29)
>
> #define TPS_STATUS_CONN_STATE_MASK GENMASK(3, 1)
> diff --git a/drivers/usb/typec/tipd/trace.h b/drivers/usb/typec/tipd/trace.h
> index 0669cca12..bea383f2d 100644
> --- a/drivers/usb/typec/tipd/trace.h
> +++ b/drivers/usb/typec/tipd/trace.h
> @@ -153,7 +153,7 @@
> { TPS_STATUS_OVERCURRENT, "OVERCURRENT" }, \
> { TPS_STATUS_GOTO_MIN_ACTIVE, "GOTO_MIN_ACTIVE" }, \
> { TPS_STATUS_BIST, "BIST" }, \
> - { TPS_STATUS_HIGH_VOLAGE_WARNING, "HIGH_VOLAGE_WARNING" }, \
> + { TPS_STATUS_HIGH_VOLTAGE_WARNING, "HIGH_VOLTAGE_WARNING" }, \
> { TPS_STATUS_HIGH_LOW_VOLTAGE_WARNING, "HIGH_LOW_VOLTAGE_WARNING" })
Consider making "HIGH_LOW_VOLTAGE_WARNING" inline with
"HIGH_VOLTAGE_WARNING", or vice versa.
>
> #define show_tps25750_status_flags(flags) \
Reviewed-by: Brigham Campbell <me@brighamcampbell.com>
next prev parent reply other threads:[~2025-05-22 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 21:48 [PATCH 1/1] usb: typec: tipd: fix typo in TPS_STATUS_HIGH_VOLAGE_WARNING macro Jihed Chaibi
2025-05-22 7:47 ` Brigham Campbell [this message]
2025-05-22 8:30 ` Greg KH
2025-05-22 11:10 ` Jihed Chaibi
2025-05-22 16:21 ` Brigham Campbell
2025-05-22 16:36 ` Greg KH
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=DA2IV4ZGT2M8.3QXO3L57VXSA5@brighamcampbell.com \
--to=me@brighamcampbell.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jihed.chaibi.dev@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skhan@linuxfoundation.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