netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] i40e: make functions static and remove dead code
Date: Thu, 12 Dec 2013 12:25:14 -0800	[thread overview]
Message-ID: <1386879914.2204.91.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20131212120759.430fab12@nehalam.linuxnetplumber.net>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On Thu, 2013-12-12 at 12:07 -0800, Stephen Hemminger wrote:
> 
> Make local functions static in the file they are used.
> 
> Remove functions i40e_aq_add_vlan and i40e_aq_remove_vlan since
> they are not used anywhere by current code.
> 
> Compile tested only.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> 
> 
> ---
>  drivers/net/ethernet/intel/i40e/i40e_adminq.c    |    6 +
>  drivers/net/ethernet/intel/i40e/i40e_common.c    |   80
> -----------------------
>  drivers/net/ethernet/intel/i40e/i40e_prototype.h |    8 --
>  3 files changed, 4 insertions(+), 90 deletions(-)

Thanks Stephen, currently I have nearly 80 i40e patches in my queue
right now which may take advantage of these functions.  If not, I will
add your patch to my queue.  I am hoping to get all these patches for
i40e out over the next couple of weeks, so if there are patches in my
queue that will take advantage of these functions, they will be pushed
soon.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-12-12 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 20:07 [PATCH net-next] i40e: make functions static and remove dead code Stephen Hemminger
2013-12-12 20:25 ` 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=1386879914.2204.91.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).