From: wengjianfeng <samirweng1979@163.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: stf_xl@wp.pl, helmut.schaa@googlemail.com, kvalo@codeaurora.org,
davem@davemloft.net, kuba@kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
wengjianfeng <wengjianfeng@yulong.com>
Subject: Re: [PATCH] rt2x00: remove duplicate word in comment
Date: Thu, 4 Feb 2021 08:30:07 +0800 [thread overview]
Message-ID: <20210204083007.000069d2@163.com> (raw)
In-Reply-To: <6bf90f62-f14e-9c4a-748b-4923fcae9bef@infradead.org>
On Wed, 3 Feb 2021 07:16:17 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 2/2/21 10:38 PM, samirweng1979 wrote:
> > From: wengjianfeng <wengjianfeng@yulong.com>
> >
> > remove duplicate word 'we' in comment
> >
> > Signed-off-by: wengjianfeng <wengjianfeng@yulong.com>
> > ---
> > drivers/net/wireless/ralink/rt2x00/rt2x00crypto.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/ralink/rt2x00/rt2x00crypto.c
> > b/drivers/net/wireless/ralink/rt2x00/rt2x00crypto.c index
> > c861811..7158152 100644 ---
> > a/drivers/net/wireless/ralink/rt2x00/rt2x00crypto.c +++
> > b/drivers/net/wireless/ralink/rt2x00/rt2x00crypto.c @@ -179,7
> > +179,7 @@ void rt2x00crypto_rx_insert_iv(struct sk_buff *skb,
> > * Make room for new data. There are 2 possibilities
> > * either the alignment is already present between
> > * the 802.11 header and payload. In that case we
> > - * we have to move the header less then the iv_len
> > + * have to move the header less then the iv_len
>
> s/then/than/
>
> > * since we can use the already available l2pad bytes
> > * for the iv data.
> > * When the alignment must be added manually we must
> >
>
>
Hi Randy,
So you means add it for byte alignment, right? if yes,just ignore
the patch. thanks.
next prev parent reply other threads:[~2021-02-04 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 6:38 [PATCH] rt2x00: remove duplicate word in comment samirweng1979
2021-02-03 15:16 ` Randy Dunlap
2021-02-04 0:30 ` wengjianfeng [this message]
2021-02-04 0:33 ` Randy Dunlap
2021-02-04 0:39 ` wengjianfeng
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=20210204083007.000069d2@163.com \
--to=samirweng1979@163.com \
--cc=davem@davemloft.net \
--cc=helmut.schaa@googlemail.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stf_xl@wp.pl \
--cc=wengjianfeng@yulong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.