netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [net-next-2.6] if_vlan.h: fix compile errors
Date: Wed, 13 Apr 2011 04:03:57 -0700	[thread overview]
Message-ID: <BANLkTimn2GfWs3tmoh+GRX6vX6tH9FpEyg@mail.gmail.com> (raw)
In-Reply-To: <20110413105758.GA2910@psychotron.orion>

On Wed, Apr 13, 2011 at 03:57, Jiri Pirko <jpirko@redhat.com> wrote:
> Thanks Jeff, this fix was already submitted by DaveM

Ah, ok.  I did not see anything in netdev patchworks and I did a
recent pull of Dave's net-next tree so I knew I had the latest.
Good to know it was caught, thanks Jiri.

>
> Wed, Apr 13, 2011 at 12:32:17PM CEST, jeffrey.t.kirsher@intel.com wrote:
>>The following commit generates compile errors becuase vlan_untag was defined
>>multiple times.
>>
>>    commit bcc6d47903612c3861201cc3a866fb604f26b8b2
>>    Author: Jiri Pirko <jpirko@redhat.com>
>>    Date:   Thu Apr 7 19:48:33 2011 +0000
>>
>>    net: vlan: make non-hw-accel rx path similar to hw-accel
>>
>>Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>>---
>> include/linux/if_vlan.h |    2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>>diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h
>>index 998b299..546d9d3 100644
>>--- a/include/linux/if_vlan.h
>>+++ b/include/linux/if_vlan.h
>>@@ -174,7 +174,7 @@ static inline bool vlan_do_receive(struct sk_buff **skb)
>>       return false;
>> }
>>
>>-inline struct sk_buff *vlan_untag(struct sk_buff *skb)
>>+static inline struct sk_buff *vlan_untag(struct sk_buff *skb)
>> {
>>       return skb;
>> }

  reply	other threads:[~2011-04-13 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 10:32 [net-next-2.6] if_vlan.h: fix compile errors Jeff Kirsher
2011-04-13 10:57 ` Jiri Pirko
2011-04-13 11:03   ` Jeff Kirsher [this message]
2011-04-13 17:46     ` 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=BANLkTimn2GfWs3tmoh+GRX6vX6tH9FpEyg@mail.gmail.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=jpirko@redhat.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).