public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vthiagar-A+ZNKFmMK5xy9aJCnZT0Uw@public•gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public•gmane.org>
Cc: <linville-2XuSBdqkA4R54TAoqtyWWQ@public•gmane.org>,
	<johannes-cdvu00un1VgdHxzADdlk8Q@public•gmane.org>,
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
	netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>
Subject: Re: [RFC V3 1/2] I'dcfg80211: Move the definition of struct mac_address up
Date: Fri, 7 Dec 2012 12:26:03 +0530	[thread overview]
Message-ID: <50C19303.5060608@qca.qualcomm.com> (raw)
In-Reply-To: <1354858735.22463.31.camel@joe-AO722>



On Friday 07 December 2012 11:08 AM, Joe Perches wrote:
> On Fri, 2012-12-07 at 09:47 +0530, Vasanthakumar Thiagarajan wrote:
>> struct mac_address will be used by ACL related configuration ops.
>
> I'd prefer that any new code _not_ use struct mac_address
> but use u8 addr[ETH_ALEN] instead.
>
> That's the most common style in the kernel.

Ok, but struct mac_address looked handy when I want
to deal with list of mac address instead using linked
list. Thanks!

Vasanth
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-12-07  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1354853850-10537-1-git-send-email-vthiagar@qca.qualcomm.com>
     [not found] ` <1354853850-10537-1-git-send-email-vthiagar-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
2012-12-07  5:38   ` [RFC V3 1/2] I'dcfg80211: Move the definition of struct mac_address up Joe Perches
2012-12-07  6:56     ` Vasanthakumar Thiagarajan [this message]
2012-12-07  8:09     ` Johannes Berg

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=50C19303.5060608@qca.qualcomm.com \
    --to=vthiagar-a+znkfmmk5xy9ajcnzt0uw@public$(echo .)gmane.org \
    --cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public$(echo .)gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public$(echo .)gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public$(echo .)gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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