public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Arvid Brodin <arvid.brodin@alten•se>
To: Stephen Hemminger <stephen@networkplumber•org>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	Stephen Hemminger <shemminger@vyatta•com>
Subject: Re: [PATCH IPROUTE] ip: Add HSR support
Date: Mon, 25 Nov 2013 20:20:47 +0100	[thread overview]
Message-ID: <5293A30F.6030407@alten.se> (raw)
In-Reply-To: <20131122173334.0ae81887@nehalam.linuxnetplumber.net>

On 2013-11-23 02:33, Stephen Hemminger wrote:
> On Fri, 8 Nov 2013 20:34:36 +0100
> Arvid Brodin <arvid.brodin@xdin•com> wrote:
>
>> This patch adds basic support for High-Availability Seamless
>> Redundancy (HSR) network devices.
>>
>> Signed-off-by: Arvid Brodin <arvid.brodin@xdin•com>
>
> Will not apply to current iproute source. The header files have been updated
> to be from current upstream (linus), and the IFLA_HSR doesn't match.

So, what's the least annoying (for everyone) way of getting the updated header
file into the kernel _and_ iproute?

I guess the iproute patch should be against net-next-for-3.13? (The HSR kernel
patch was picked up into 3.13-rc1.)

And the updated kernel patch (with the .fill_info routine implemented and the
updated header file), where do I send that?


--
Arvid Brodin | Consultant (Linux)
ALTEN | Knarrarnäsgatan 7 | SE-164 40 Kista | Sweden
arvid.brodin@alten•se | www.alten.se/en/

________________________________
Xdin is changing its name. From 25 November 2013 we will be known as Alten. Read more at www.alten.se

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 19:34 [PATCH IPROUTE] ip: Add HSR support Arvid Brodin
2013-11-23  1:33 ` Stephen Hemminger
2013-11-25 19:20   ` Arvid Brodin [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=5293A30F.6030407@alten.se \
    --to=arvid.brodin@alten$(echo .)se \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=shemminger@vyatta$(echo .)com \
    --cc=stephen@networkplumber$(echo .)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