From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "shaikh.kamal" <shaikhkamal2012@gmail.com>
Cc: "David E . Box" <david.e.box@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/ABI: intel_pmt: fix 'threashold' spelling
Date: Mon, 27 Jul 2026 12:12:40 +0300 (EEST) [thread overview]
Message-ID: <3391ce45-1f3b-a6b9-92c8-2b94a801c6d9@linux.intel.com> (raw)
In-Reply-To: <20260726063734.19944-1-shaikhkamal2012@gmail.com>
On Sun, 26 Jul 2026, shaikh.kamal wrote:
> Fix spelling error reported by codespell: threashold -> threshold.
> No functional change.
>
> Signed-off-by: shaikh.kamal <shaikhkamal2012@gmail.com>
Does your name contain . ??
For more information about signing off you change, please see
Documentation/process/submitting-patches.rst
> ---
> Documentation/ABI/testing/sysfs-class-intel_pmt-features | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-intel_pmt-features b/Documentation/ABI/testing/sysfs-class-intel_pmt-features
> index cddb30e5bdf6..476ba070fb1e 100644
> --- a/Documentation/ABI/testing/sysfs-class-intel_pmt-features
> +++ b/Documentation/ABI/testing/sysfs-class-intel_pmt-features
> @@ -121,7 +121,7 @@ Example 'caps' content for the 'tracing' feature:
> watcher Available: Yes
> crashlog Available: No
> streaming Available: No
> - threashold Available: No
> + threshold Available: No
I think that anyone can see what's wrong with that alignment. Perhaps you
didn't even look but sent the patch blindly!?! :-/
Please read through your own changes to avoid a reviewer having to point
out trivial things like this to you. It wastes everyone's time (including
yours) to send obviously half-baked patches to review. :-(
--
i.
next prev parent reply other threads:[~2026-07-27 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 6:37 shaikh.kamal
2026-07-27 9:12 ` Ilpo Järvinen [this message]
2026-07-30 16:38 ` shaikh kamaluddin
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=3391ce45-1f3b-a6b9-92c8-2b94a801c6d9@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shaikhkamal2012@gmail.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
all inboxes | Powered by JetHome®