From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ixgbe: Remove unnecessary #ifdef CONFIG_DEBUG_FS tests
Date: Mon, 08 Apr 2013 11:47:36 -0700 [thread overview]
Message-ID: <1365446856.2048.0.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1365384453.8922.20.camel@joe-AO722>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
On Sun, 2013-04-07 at 18:27 -0700, Joe Perches wrote:
> Add some empty static inlines instead to make
> the code more readable.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe.h | 5 +++++
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 10 ----------
> 2 files changed, 5 insertions(+), 10 deletions(-)
Thanks Joe, I have added the patch to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-08 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 1:27 [PATCH net-next] ixgbe: Remove unnecessary #ifdef CONFIG_DEBUG_FS tests Joe Perches
2013-04-08 18:47 ` Jeff Kirsher [this message]
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=1365446856.2048.0.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=joe@perches.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).