public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Bourbié" <benoit.bourbie@gmail.com>
To: inaky.perez-gonzalez@intel.com
Cc: wimax@linuxwimax.org, netdev@vger.kernel.org,
	"Benoît Bourbié" <benoit.bourbie@gmail.com>
Subject: [PATCH] net : fix typo
Date: Sun, 14 Apr 2013 14:33:12 -0500	[thread overview]
Message-ID: <1365967993-3945-1-git-send-email-benoit.bourbie@gmail.com> (raw)

Fixed some grammar mistakes.


Signed-off-by: Benoît Bourbié <benoit.bourbie@gmail.com>
---
 include/net/wimax.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/net/wimax.h b/include/net/wimax.h
index bbb74f9..4588407 100644
--- a/include/net/wimax.h
+++ b/include/net/wimax.h
@@ -103,7 +103,7 @@
  * over multicast groups. This allows to have multiple applications
  * monitoring them.
  *
- * Each command/signal gets assigned it's own attribute policy. This
+ * Each command/signal gets assigned its own attribute policy. This
  * way the validator will verify that all the attributes in there are
  * only the ones that should be for each command/signal. Thing of an
  * attribute mapping to a type+argumentname for each command/signal.
@@ -123,7 +123,7 @@
  *
  * If network interface X is a WiMAX device, there will be a Generic
  * Netlink family named "WiMAX X" and the device will present a
- * "wimax" directory in it's network sysfs directory
+ * "wimax" directory in its network sysfs directory
  * (/sys/class/net/DEVICE/wimax) [used by HAL].
  *
  * The inexistence of any of these means the device does not support
@@ -228,7 +228,7 @@
  * WiMAX stack.
  *
  * When initializing the hardware (_probe), after calling
- * wimax_dev_add(), query the device for it's RF Kill switches status
+ * wimax_dev_add(), query the device for its RF Kill switches status
  * and feed it back to the WiMAX stack using
  * wimax_report_rfkill_{hw,sw}(). If any switch is missing, always
  * report it as ON.
@@ -306,7 +306,7 @@ struct wimax_dev;
  *     DRIVERNAME-BUSNAME:BUSID (dev->bus->name, dev->bus_id).
  *
  * @id_table_node: [private] link to the list of wimax devices kept by
- *     id-table.c. Protected by it's own spinlock.
+ *     id-table.c. Protected by its own spinlock.
  *
  * @mutex: [private] Serializes all concurrent access and execution of
  *     operations.
-- 
1.8.2.470.g21ccebe.dirty

             reply	other threads:[~2013-04-14 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 19:33 Benoît Bourbié [this message]
2013-04-14 19:33 ` [PATCH] net : fix typo Benoît Bourbié
2013-04-14 19:38   ` David Miller
2013-04-14 21:13     ` Benoît Bourbié

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=1365967993-3945-1-git-send-email-benoit.bourbie@gmail.com \
    --to=benoit.bourbie@gmail.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wimax@linuxwimax.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