public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels•com>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: David Miller <davem@davemloft•net>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: Iproute2 build broken by current kernel headers
Date: Wed, 11 Jan 2012 22:27:51 +0400	[thread overview]
Message-ID: <4F0DD4A7.1080204@parallels.com> (raw)
In-Reply-To: <20120111102400.178baee6@nehalam.linuxnetplumber.net>

> These patches will have to be redone to work with the revised include
> files. The iproute2 changes are not acceptable as is because they do not support
> older kernels.
> 
> It is critical that the resulting code work on both old and new
> kernels. In other words, when the new ss command is built (using your
> patches and 3.3 headers), it:
>  * SHOULD send new diag requests to kernel and be able to display
>    the new UNIX domain info
>  * MUST still work when run against old 3.2 kernel.
> 
> This means the code should send new request first, and if that generates
> an error fallback (silently) to the old message format.

OK, I will rework the patches in this way.

Thanks,
Pavel

      reply	other threads:[~2012-01-11 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 18:54 Iproute2 build broken by current kernel headers Stephen Hemminger
2012-01-10 19:07 ` Stephen Hemminger
2012-01-11  6:34   ` Pavel Emelyanov
2012-01-11  6:39     ` David Miller
2012-01-11  6:58       ` Pavel Emelyanov
2012-01-11  7:03         ` David Miller
2012-01-11 18:24     ` Stephen Hemminger
2012-01-11 18:27       ` Pavel Emelyanov [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=4F0DD4A7.1080204@parallels.com \
    --to=xemul@parallels$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=shemminger@vyatta$(echo .)com \
    /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