All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Li <lovelylich@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [PATCH] net: replace dev_base with dev_base_lock in comment typo
Date: Wed, 25 Jun 2014 06:07:10 +0000	[thread overview]
Message-ID: <1403676430-22640-1-git-send-email-lovelylich@gmail.com> (raw)

There is no dev_base in dev.c now. Any time we access dev_base_head,
we should hold dev_base_lock or rtnl_lock().So, change the comment
from 'dev_base' into 'dev_base_lock'.

Signed-off-by: Yi Li <lovelylich@gmail.com>
---
 net/core/dev.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/core/dev.c b/net/core/dev.c
index a04b12f..1a95e08 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -953,7 +953,7 @@ EXPORT_SYMBOL(dev_valid_name);
  *
  *	Passed a format string - eg "lt%d" it will try and find a suitable
  *	id. It scans list of devices to build up a free map, then chooses
- *	the first empty slot. The caller must hold the dev_base or rtnl lock
+ *	the first empty slot. The caller must hold the dev_base_lock or rtnl lock
  *	while allocating the name and adding the device in order to avoid
  *	duplicates.
  *	Limited to bits_per_byte * page size devices (ie 32K on most platforms).
@@ -1018,7 +1018,7 @@ static int __dev_alloc_name(struct net *net, const char *name, char *buf)
  *
  *	Passed a format string - eg "lt%d" it will try and find a suitable
  *	id. It scans list of devices to build up a free map, then chooses
- *	the first empty slot. The caller must hold the dev_base or rtnl lock
+ *	the first empty slot. The caller must hold the dev_base_lock or rtnl lock
  *	while allocating the name and adding the device in order to avoid
  *	duplicates.
  *	Limited to bits_per_byte * page size devices (ie 32K on most platforms).
-- 
1.9.3


                 reply	other threads:[~2014-06-25  6:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1403676430-22640-1-git-send-email-lovelylich@gmail.com \
    --to=lovelylich@gmail.com \
    --cc=kernel-janitors@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 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.