netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vlad Zolotarov <vladz@cloudius-systems.com>
Subject: Re: [PATCH] net: Fix typos and whitespace.
Date: Wed, 23 Mar 2016 08:55:35 -0500	[thread overview]
Message-ID: <20160323135535.GA18845@localhost> (raw)
In-Reply-To: <20160323134530.18742.35082.stgit@bhelgaas-glaptop2.roam.corp.google.com>

[+cc Vlad]

On Wed, Mar 23, 2016 at 08:45:30AM -0500, Bjorn Helgaas wrote:
> Fix typos.  Capitalize CPU, NAPI, RCU consistently.  Align structure
> indentation.  No functional change intended; only comment and whitespace
> changes.
> 
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
>  include/linux/netdevice.h |  215 ++++++++++++++++++++++-----------------------

> @@ -920,7 +920,7 @@ struct tc_to_netdev {
>   *
>   *      Enable or disable the VF ability to query its RSS Redirection Table and
>   *      Hash Key. This is needed since on some devices VF share this information
> - *      with PF and querying it may adduce a theoretical security risk.
> + *      with PF and querying it may introduce a theoretical security risk.
>   * int (*ndo_set_vf_rss_query_en)(struct net_device *dev, int vf, bool setting)

Most of these are obvious typo fixes, but I want to point out this one
in particular because "adduce" is a real word.  It's possible that's
what Vlad intended in 01a3d796813d ("if_link: Add an additional
parameter to ifla_vf_info for RSS querying"), though it doesn't quite
seem to fit.  Vlad, if you did intend "adduce", my apologies in
advance.

Bjorn

  reply	other threads:[~2016-03-23 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 13:45 [PATCH] net: Fix typos and whitespace Bjorn Helgaas
2016-03-23 13:55 ` Bjorn Helgaas [this message]
2016-03-23 17:16   ` Vlad Zolotarov
2016-03-23 18:27 ` David Miller
2016-03-24  0:28   ` Tom Herbert
2016-03-24  0:55     ` David Miller

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=20160323135535.GA18845@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vladz@cloudius-systems.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).