From: Jun Miao <jun.miao@windriver.com>
To: Joe Perches <joe@perches.com>, 3chas3@gmail.com
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atm: horizon: Fix spelling mistakes in TX comment
Date: Sat, 7 Aug 2021 21:57:08 +0800 [thread overview]
Message-ID: <d50b58fe-298b-a285-59ec-2d3aa275d221@windriver.com> (raw)
In-Reply-To: <0b52c87bb939fe45c1cf07fe9c3409e927138046.camel@perches.com>
On 8/7/21 9:21 PM, Joe Perches wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> On Sat, 2021-08-07 at 20:49 +0800, Jun Miao wrote:
>> It's "mustn't", not "musn't", meaning "shall not".
>> Let's fix that.
> Perhaps more useful to change to 'must not' for the
> non-native speaker.
Ok, V2 : Suggested-by: Joe Perches <joe@perches.com>
Thanks
Jun
>> diff --git a/drivers/atm/horizon.c b/drivers/atm/horizon.c
> []
What's mean this [] ?
>> @@ -2167,10 +2167,10 @@ static int hrz_open (struct atm_vcc *atm_vcc)
>>
>>
>> // Part of the job is done by atm_pcr_goal which gives us a PCR
>> // specification which says: EITHER grab the maximum available PCR
>> - // (and perhaps a lower bound which we musn't pass), OR grab this
>> + // (and perhaps a lower bound which we mustn't pass), OR grab this
>> // amount, rounding down if you have to (and perhaps a lower bound
>> - // which we musn't pass) OR grab this amount, rounding up if you
>> - // have to (and perhaps an upper bound which we musn't pass). If any
>> + // which we mustn't pass) OR grab this amount, rounding up if you
>> + // have to (and perhaps an upper bound which we mustn't pass). If any
>> // bounds ARE passed we fail. Note that rounding is only rounding to
>> // match device limitations, we do not round down to satisfy
>> // bandwidth availability even if this would not violate any given
>
prev parent reply other threads:[~2021-08-07 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 12:49 Jun Miao
2021-08-07 13:21 ` Joe Perches
2021-08-07 13:57 ` Jun Miao [this message]
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=d50b58fe-298b-a285-59ec-2d3aa275d221@windriver.com \
--to=jun.miao@windriver.com \
--cc=3chas3@gmail.com \
--cc=joe@perches.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®