linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ajith P V <ajithpv.linux@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Ajith P V <ajithpv.linux@gmail.com>
Subject: [PATCH] staging: fwserial: rearrange comment to avoid warning
Date: Wed, 19 Jan 2022 14:11:59 +0530	[thread overview]
Message-ID: <20220119084159.5759-1-ajithpv.linux@gmail.com> (raw)

fwserial.h comment contains word "bits" 2 times together.
The sentence required this however it produce warning.
Change the comment to make it proper.

Signed-off-by: Ajith P V <ajithpv.linux@gmail.com>
---
 drivers/staging/fwserial/fwserial.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/fwserial/fwserial.h b/drivers/staging/fwserial/fwserial.h
index 1d15f183e0fa..ae7cf84ceafc 100644
--- a/drivers/staging/fwserial/fwserial.h
+++ b/drivers/staging/fwserial/fwserial.h
@@ -203,7 +203,7 @@ struct fwconsole_ops {
  * @break_last: timestamp in jiffies from last emit_breaks
  * @hangup: work responsible for HUPing when carrier is dropped/lost
  * @mstatus: loose virtualization of LSR/MSR
- *         bits 15..0  correspond to TIOCM_* bits
+ *         bits 15..0  correspond to bits TIOCM_*
  *         bits 19..16 reserved for mctrl
  *         bit 20      OOB_TX_THROTTLE
  *	   bits 23..21 reserved
-- 
2.17.1


             reply	other threads:[~2022-01-19  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  8:41 Ajith P V [this message]
2022-01-19 15:19 ` [PATCH] staging: fwserial: rearrange comment to avoid warning Randy Dunlap
2022-01-19 17:57   ` Dan Carpenter

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=20220119084159.5759-1-ajithpv.linux@gmail.com \
    --to=ajithpv.linux@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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).