public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@Voltaire•com>
To: Jay Vosburgh <fubar@us•ibm.com>
Cc: netdev@vger•kernel.org, kaber@trash•net
Subject: Re: more findings/questions on vlans/bonds
Date: Sun, 26 Apr 2009 17:14:15 +0300	[thread overview]
Message-ID: <49F46C37.2050001@Voltaire.com> (raw)
In-Reply-To: <13724.1240520690@death.nxdomain.ibm.com>

Jay Vosburgh wrote:
>         So, here's a patch with a description.  This resolves the
> bonding problem for me; it might have other undesirable side effects,
> though.  It's debatable whether it's really necessary, but it does make
> the VLAN device behave more like a real network device in this case:
> 
> [PATCH] vlan: update vlan carrier state for admin up/down

Jay, I just can't apply the patch on 2.6.30-rc2 it all fails, which
is quite weird since the code (e.g net/8021q/vlan.c) hasn't gone through
many changes recently - any idea what I do wrong?

Or.

> # patch --dry-run -p 1 < /tmp/vlans_bonds.patch
> patching file net/8021q/vlan.c
> Hunk #1 FAILED at 492.
> Hunk #2 FAILED at 508.
> 2 out of 2 hunks FAILED -- saving rejects to file net/8021q/vlan.c.rej
> patching file net/8021q/vlan_dev.c
> Hunk #1 FAILED at 462.
> Hunk #2 FAILED at 472.
> Hunk #3 FAILED at 494.
> Hunk #4 FAILED at 615.
> 4 out of 4 hunks FAILED -- saving rejects to file net/8021q/vlan_dev.c.rej


      parent reply	other threads:[~2009-04-26 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  9:14 more findings/questions on vlans/bonds Or Gerlitz
2009-04-07  9:16 ` Or Gerlitz
2009-04-07 14:13 ` Jay Vosburgh
2009-04-16 14:17   ` Or Gerlitz
2009-04-23 21:04 ` Jay Vosburgh
2009-04-24 15:22   ` Patrick McHardy
2009-04-26  8:21   ` Or Gerlitz
2009-04-26 14:14   ` Or Gerlitz [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=49F46C37.2050001@Voltaire.com \
    --to=ogerlitz@voltaire$(echo .)com \
    --cc=fubar@us$(echo .)ibm.com \
    --cc=kaber@trash$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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