From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Al Cooper <alcooperx@gmail.com>,
Sasi Kumar <sasi.kumar@broadcom.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: [PATCH 11/11] usb: gadget: bdc: fix checkpatch.pl repeated word warning
Date: Fri, 25 Sep 2020 13:58:19 +0800 [thread overview]
Message-ID: <1601013499-28920-11-git-send-email-chunfeng.yun@mediatek.com> (raw)
In-Reply-To: <1601013499-28920-1-git-send-email-chunfeng.yun@mediatek.com>
fix the warning:
WARNING:REPEATED_WORD: Possible repeated word: 'and'
Change-Id: I48d89c4c001e11ae13d8ff2190c51328a3faaf46
Cc: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
---
drivers/usb/gadget/udc/bdc/bdc_ep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/bdc/bdc_ep.c b/drivers/usb/gadget/udc/bdc/bdc_ep.c
index d227d26..8e2f20b 100644
--- a/drivers/usb/gadget/udc/bdc/bdc_ep.c
+++ b/drivers/usb/gadget/udc/bdc/bdc_ep.c
@@ -1405,7 +1405,7 @@ static int ep0_set_sel(struct bdc *bdc,
}
/*
- * Queue a 0 byte bd only if wLength is more than the length and and length is
+ * Queue a 0 byte bd only if wLength is more than the length and length is
* a multiple of MaxPacket then queue 0 byte BD
*/
static int ep0_queue_zlp(struct bdc *bdc)
--
1.8.1.1.dirty
next prev parent reply other threads:[~2020-09-25 6:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 5:58 [PATCH 01/11] usb: gadget: bdc: fix improper SPDX comment style for header file Chunfeng Yun
2020-09-25 5:58 ` [PATCH 02/11] usb: gadget: bdc: remove bdc_ep_set_halt() declaration Chunfeng Yun
2020-09-25 5:58 ` [PATCH 03/11] usb: gadget: bdc: prefer pointer dereference to pointer type Chunfeng Yun
2020-09-25 5:58 ` [PATCH 04/11] usb: gadget: bdc: fix warning of embedded function name Chunfeng Yun
2020-09-25 5:58 ` [PATCH 05/11] usb: gadget: bdc: fix check warning of block comments alignment Chunfeng Yun
2020-09-25 5:58 ` [PATCH 06/11] usb: gadget: bdc: add identifier name for function declaraion Chunfeng Yun
2020-09-25 5:58 ` [PATCH 07/11] usb: gadget: bdc: avoid precedence issues Chunfeng Yun
2020-09-25 5:58 ` [PATCH 08/11] usb: gadget: bdc: use the BIT macro to define bit filed Chunfeng Yun
2020-09-25 5:58 ` [PATCH 09/11] usb: gadget: bdc: fix checkpatch.pl tab warning Chunfeng Yun
2020-09-25 5:58 ` [PATCH 10/11] usb: gadget: bdc: fix checkpatch.pl spacing error Chunfeng Yun
2020-09-25 5:58 ` Chunfeng Yun [this message]
2020-09-25 6:10 ` [PATCH 01/11] usb: gadget: bdc: fix improper SPDX comment style for header file Chunfeng Yun
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=1601013499-28920-11-git-send-email-chunfeng.yun@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=alcooperx@gmail.com \
--cc=balbi@kernel.org \
--cc=colin.king@canonical.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=natechancellor@gmail.com \
--cc=sasi.kumar@broadcom.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;
as well as URLs for NNTP newsgroup(s).