From: Ben Hutchings <bhutchings@solarflare.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, gospo@redhat.com,
Greg Rose <gregory.v.rose@intel.com>
Subject: Re: [RFC PATCH v2 01/12] ixgbevf: Macros, data structures, useful defines and registers
Date: Mon, 21 Dec 2009 18:38:22 +0000 [thread overview]
Message-ID: <1261420702.2782.3.camel@achroite.uk.solarflarecom.com> (raw)
In-Reply-To: <20091218225043.10698.58897.stgit@localhost.localdomain>
On Fri, 2009-12-18 at 14:51 -0800, Jeff Kirsher wrote:
> From: Greg Rose <gregory.v.rose@intel.com>
>
> These two headers define the commonly used macros, data structures,
> register bits and register offsets used by the ixgbevf driver on the
> 82599 virtual function device
>
[...]
> diff --git a/drivers/net/ixgbevf/defines.h b/drivers/net/ixgbevf/defines.h
> new file mode 100644
> index 0000000..b111771
> --- /dev/null
> +++ b/drivers/net/ixgbevf/defines.h
[...]
> +/* Check whether address is multicast. This is little-endian specific check.*/
> +#define IXGBE_IS_MULTICAST(Address) \
> + (bool)(((u8 *)(Address))[0] & ((u8)0x01))
> +
> +/* Check whether an address is broadcast. */
> +#define IXGBE_IS_BROADCAST(Address) \
> + ((((u8 *)(Address))[0] == ((u8)0xFF)) && \
> + (((u8 *)(Address))[1] == ((u8)0xFF)))
[...]
Why not use is_multicast_ether_addr() and is_broadcast_ether_addr()?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-12-21 18:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 22:51 [RFC PATCH v2 01/12] ixgbevf: Macros, data structures, useful defines and registers Jeff Kirsher
2009-12-18 22:51 ` [RFC PATCH v2 02/12] ixgbevf: 82599 Virtual Function core functions and header Jeff Kirsher
2009-12-21 5:03 ` Simon Horman
2009-12-23 20:22 ` Ben Hutchings
2009-12-23 21:36 ` Rose, Gregory V
2009-12-18 22:51 ` [RFC PATCH v2 03/12] ixgbevf: Mailbox communication Jeff Kirsher
2009-12-23 20:28 ` Ben Hutchings
2009-12-23 21:38 ` Rose, Gregory V
2009-12-18 22:51 ` [RFC PATCH v2 04/12] ixgbevf: Driver main and ethool interface module and main header Jeff Kirsher
2009-12-21 7:59 ` Simon Horman
2009-12-21 18:18 ` Rose, Gregory V
2009-12-23 0:05 ` Rose, Gregory V
2009-12-18 22:52 ` [RFC PATCH v2 05/12] ixgbevf: Driver Makefile Jeff Kirsher
2009-12-18 22:52 ` [RFC PATCH v2 06/12] ixgbevf: Kconfig, Makefile and Documentation Jeff Kirsher
2009-12-18 22:52 ` [RFC PATCH v2 07/12] ixgbe: Mailbox header and code module Jeff Kirsher
2009-12-18 22:53 ` [RFC PATCH v2 08/12] ixgbe: Add SR-IOV register, structure and bit defines Jeff Kirsher
2009-12-18 22:53 ` [RFC PATCH v2 09/12] ixgbe: Add SR-IOV specific features Jeff Kirsher
2009-12-18 22:53 ` [RFC PATCH v2 10/12] ixgbe: Add SR-IOV specific modules to driver Makefile Jeff Kirsher
2009-12-18 22:53 ` [RFC PATCH v2 11/12] ixgbe: Add SR-IOV feature enablement code Jeff Kirsher
2009-12-18 22:54 ` [RFC PATCH v2 12/12] ixgbe: Add SR-IOV features to main module Jeff Kirsher
2009-12-21 18:38 ` Ben Hutchings [this message]
2009-12-21 18:51 ` [RFC PATCH v2 01/12] ixgbevf: Macros, data structures, useful defines and registers Rose, Gregory V
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=1261420702.2782.3.camel@achroite.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=gospo@redhat.com \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.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).