From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: [PATCH bluetooth-next] ieee802154/cc2520: check for return values in cc2520_filter()
Date: Tue, 9 Jun 2015 12:02:02 +0200 [thread overview]
Message-ID: <20150609100158.GB1402@omega> (raw)
In-Reply-To: <5576B71F.4030905@osg.samsung.com>
On Tue, Jun 09, 2015 at 11:51:27AM +0200, Stefan Schmidt wrote:
>
> Well, imho its not a subsubsystem but rather a simple file. Also using
> subsytem: file: looks quite alien to me. Anyway, matter of taste, nothing to
> argue about. Fixed in v2.
>
sorry, I never see foo/bar: things at begin of the subject. I see David
Miller on netdev which only mentioned that the usually way is
"subsystem:", when somebody complete forgets to add this. For me it doesn't matter
if somebody will more specify it like "subsystem: drivers: file:" or
"subsystem: file: ..." that's everything fine, but don making a '/' somewhere.
But I see also people which tags "6lowpan:" only and then it touched
net/ieee802154/6lowpan only. That's confusing, it should be then
"ieee802154: 6lowpan:". If it touched the net/6lowpan it should be
"6lowpan:" only.
I think I need to make some harder rules to check on this.
- Alex
next prev parent reply other threads:[~2015-06-09 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:11 [PATCH bluetooth-next] ieee802154/cc2520: check for return values in cc2520_filter() Stefan Schmidt
2015-06-09 9:21 ` Varka Bhadram
2015-06-09 9:51 ` Stefan Schmidt
2015-06-09 10:02 ` Alexander Aring [this message]
2015-06-09 11:50 ` Stefan Schmidt
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=20150609100158.GB1402@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@osg.samsung.com \
--cc=varkabhadram@gmail.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