From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: Mitch, e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Bruce Allan <bruce.w.allan@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org,
John Ronciak <john.ronciak@intel.com>
Subject: Re: [PATCH net-next 2/9] e100: Convert uses of __constant_<foo> to <foo>
Date: Wed, 12 Mar 2014 13:50:23 -0700 [thread overview]
Message-ID: <1394657423.2167.4.camel@jtkirshe-mobl> (raw)
In-Reply-To: <b7d59e4e50e0e90546ca66d2865d52552be1e553.1394644825.git.joe@perches.com>
[-- Attachment #1.1: Type: text/plain, Size: 394 bytes --]
On Wed, 2014-03-12 at 10:22 -0700, Joe Perches wrote:
> The use of __constant_<foo> has been unnecessary for quite awhile now.
>
> Make these uses consistent with the rest of the kernel.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/net/ethernet/intel/e100.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks Joe, I will add this to my queue.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 370 bytes --]
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
[-- Attachment #3: Type: text/plain, Size: 257 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2014-03-12 20:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 17:22 [PATCH net-next 0/9] drivers/net: Convert uses of __constant_<foo> to <foo> Joe Perches
2014-03-12 17:22 ` [PATCH net-next 1/9] brocade: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 2/9] e100: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher [this message]
2014-03-12 17:22 ` [PATCH net-next 3/9] igb: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 4/9] igbvf: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 5/9] ixgbe: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 6/9] ixgbevf: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 20:51 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 7/9] xilinx: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 8/9] lg-vl600: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 9/9] ath9k: " Joe Perches
2014-03-12 19:29 ` David Miller
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=1394657423.2167.4.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=joe@perches.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).