From: David Miller <davem@davemloft.net>
To: alex.bluesman.smirnov@gmail.com
Cc: netdev@vger.kernel.org, dbaryshkov@gmail.com
Subject: Re: [PATCH net-next v4 02/13] mac802154: allocation of ieee802154 device
Date: Mon, 14 May 2012 18:28:24 -0400 (EDT) [thread overview]
Message-ID: <20120514.182824.2287894454156614132.davem@davemloft.net> (raw)
In-Reply-To: <1336831165-23944-3-git-send-email-alex.bluesman.smirnov@gmail.com>
From: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Date: Sat, 12 May 2012 17:59:14 +0400
> Add interface for device drivers to allocate and register ieee802154
> compatible device.
>
> This code is based on net/mac80211/main.c file
>
> Signed-off-by: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Sorry, this needs to be fixed up.
I can almost understand using a comment formatting style I
disagree with, if you do so consistently.
But formatting them in THREE completely different ways? Give me a
break:
> + /* As in mac80211 slaves list is modified:
> + * 1) under the RTNL
> + * 2) protected by slaves_mtx;
> + * 3) in an RCU manner
> + *
> + * So atomic readers can use any of this protection methods
> + */
...
> + /* This one is used for scanning and other
> + * jobs not to be interfered with serial driver */
...
> + /*
> + * The following flag is also modified under slaves_mtx and RTNL,
> + * so you can read them using any of protection methods.
> + */
> + /*
> + * SoftMAC device is registered and running. One can add
> + * subinterfaces.
> + */
That's just beyond silly, and the last two comments are right next to
eachother just combine them to one.
Go over your entire patch set and make sure that all of your comments
are of the form:
/* Like
* this.
*/
next prev parent reply other threads:[~2012-05-14 22:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 13:59 [PATCH net-next v4 0/13] basic ieee802.15.4 mac support Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 01/13] mac802154: basic ieee802.15.4 device structures Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 02/13] mac802154: allocation of ieee802154 device Alexander Smirnov
2012-05-14 22:28 ` David Miller [this message]
2012-05-12 13:59 ` [PATCH net-next v4 03/13] mac802154: RX data path Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 04/13] mac802154: TX " Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 05/13] mac802154: define reduced mlme operations Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 06/13] mac802154: slave interfaces definition Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 07/13] mac802154: declare reduced mlme operations Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 08/13] mac802154: basic mib support Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 09/13] ieee802154: interface type to be added Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 10/13] mac802154: slaves manipulation routine Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 11/13] mac802154: monitor device support Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 12/13] drivers/ieee802154: IEEE 802.15.4 loopback driver Alexander Smirnov
2012-05-12 13:59 ` [PATCH net-next v4 13/13] Documentation/networking/ieee802154: update MAC chapter Alexander Smirnov
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=20120514.182824.2287894454156614132.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=dbaryshkov@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).