Linux IIO development
 help / color / mirror / Atom feed
From: Colin Ian King <colin.i.king@gmail.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
	William Breathitt Gray <william.gray@linaro.org>,
	linux-iio@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] tools/counter: Fix spelling mistake "componend" -> "component"
Date: Tue, 19 Dec 2023 13:30:15 +0000	[thread overview]
Message-ID: <20231219133015.365943-1-colin.i.king@gmail.com> (raw)

There are two spelling mistakes in the help text. Fix them.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 tools/counter/counter_watch_events.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/counter/counter_watch_events.c b/tools/counter/counter_watch_events.c
index 3898fe7e35ec..37d1b4b3e63d 100644
--- a/tools/counter/counter_watch_events.c
+++ b/tools/counter/counter_watch_events.c
@@ -120,8 +120,8 @@ static void print_usage(void)
 		"  evt_capture                (COUNTER_EVENT_CAPTURE)\n"
 		"\n"
 		"  chan=<n>                   channel <n> for this watch [default: 0]\n"
-		"  id=<n>                     componend id <n> for this watch [default: 0]\n"
-		"  parent=<n>                 componend parent <n> for this watch [default: 0]\n"
+		"  id=<n>                     component id <n> for this watch [default: 0]\n"
+		"  parent=<n>                 component parent <n> for this watch [default: 0]\n"
 		"\n"
 		"Example with two watched events:\n\n"
 		"counter_watch_events -d \\\n"
-- 
2.39.2


             reply	other threads:[~2023-12-19 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 13:30 Colin Ian King [this message]
2023-12-20 15:52 ` [PATCH][next] tools/counter: Fix spelling mistake "componend" -> "component" Fabrice Gasnier
2023-12-20 16:41 ` William Breathitt Gray

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=20231219133015.365943-1-colin.i.king@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.gray@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