From: David Miller <davem@davemloft.net>
To: xemul@parallels.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: Iproute2 build broken by current kernel headers
Date: Tue, 10 Jan 2012 23:03:52 -0800 (PST) [thread overview]
Message-ID: <20120110.230352.1291750287024833314.davem@davemloft.net> (raw)
In-Reply-To: <4F0D332B.3090105@parallels.com>
From: Pavel Emelyanov <xemul@parallels.com>
Date: Wed, 11 Jan 2012 10:58:51 +0400
> On 01/11/2012 10:39 AM, David Miller wrote:
>> You've very much handled backwards compatability terribly in these pathces,
>> I should have forced you let them cook for another full release cycle.
>> :-/
>
> Do I have 24 hours for fixing this?
You do.
next prev parent reply other threads:[~2012-01-11 7:03 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 [this message]
2012-01-11 18:24 ` Stephen Hemminger
2012-01-11 18:27 ` Pavel Emelyanov
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=20120110.230352.1291750287024833314.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=xemul@parallels.com \
/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).