From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Keenan Salandy <keenansalandy@gmail.com>
Cc: bleung@chromium.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] platform/chrome: Fix typo in CROS_USBPD_NOTIFY help text
Date: Wed, 23 Jul 2025 23:11:47 +0000 [thread overview]
Message-ID: <aIFsM5tFwgDu3HXu@google.com> (raw)
In-Reply-To: <20250723140930.1443-1-keenansalandy@gmail.com>
On Wed, Jul 23, 2025 at 10:09:30AM -0400, Keenan Salandy wrote:
> Correct the misspelling "platorms" to "platforms" in the help text
> for the CROS_USBPD_NOTIFY Kconfig option.
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/1] platform/chrome: Fix typo in CROS_USBPD_NOTIFY help text
commit: cc2d5b72b13b3af2b9b4bed3d5dfd0de14414230
Thanks!
prev parent reply other threads:[~2025-07-23 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 14:09 [PATCH] platform/chrome: Fix typo in CROS_USBPD_NOTIFY help text Keenan Salandy
2025-07-23 23:11 ` Tzung-Bi Shih [this message]
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=aIFsM5tFwgDu3HXu@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=keenansalandy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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;
as well as URLs for NNTP newsgroup(s).