From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org"
<benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Subject: Re: [PATCH rdma-core] Fix typo 'bandwith' -> 'bandwidth'
Date: Tue, 12 Dec 2017 15:24:04 +0000 [thread overview]
Message-ID: <1513092243.3704.0.camel@wdc.com> (raw)
In-Reply-To: <20171212101525.29108-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
On Tue, 2017-12-12 at 11:15 +0100, Benjamin Drung wrote:
> Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
> ---
> libibverbs/man/ibv_query_device_ex.3 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libibverbs/man/ibv_query_device_ex.3 b/libibverbs/man/ibv_query_device_ex.3
> index 1172523a..3c64abf3 100644
> --- a/libibverbs/man/ibv_query_device_ex.3
> +++ b/libibverbs/man/ibv_query_device_ex.3
> @@ -125,7 +125,7 @@ utilization and small packets will be harmed.
>
> For instance, with a 128 byte cache line size, the transfer of any
> packets less than 128 bytes will require a full 128 transfer on PCI,
> -pontentially doubling the required PCI-E bandwith.
> +pontentially doubling the required PCI-E bandwidth.
It seems to me like there is another typo in the same line, namely "pontentially".
Shouldn't that typo be fixed too?
Bart.
next prev parent reply other threads:[~2017-12-12 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:15 [PATCH rdma-core] Fix typo 'bandwith' -> 'bandwidth' Benjamin Drung
[not found] ` <20171212101525.29108-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-12-12 15:24 ` Bart Van Assche [this message]
[not found] ` <1513092243.3704.0.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-20 18:30 ` [PATCH rdma-core v2] Fix typos 'pontentially' and 'bandwith' Benjamin Drung
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=1513092243.3704.0.camel@wdc.com \
--to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
--cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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