From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: Daniel Borkmann <daniel@iogearbox•net>, shemminger@vyatta•com
Cc: netdev@vger•kernel.org, Julien Floret <julien.floret@6wind•com>
Subject: Re: [PATCH iproute2] tc: fix compilation with old gcc (< 4.6)
Date: Thu, 7 Jan 2016 17:21:50 +0100 [thread overview]
Message-ID: <568E909E.1080409@6wind.com> (raw)
In-Reply-To: <568E6EA7.6080304@iogearbox.net>
Le 07/01/2016 14:56, Daniel Borkmann a écrit :
> Btw, for iproute2's net-next branch there're couple of other occasions
> as well. Stephen, how do you prefer to handle this? Should a separate
> patch be done against net-next branch to reduce merge conflicts?
Thank you Daniel for noticing it.
next prev parent reply other threads:[~2016-01-07 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 13:03 [PATCH iproute2] tc: fix compilation with old gcc (< 4.6) Nicolas Dichtel
2016-01-07 13:31 ` Daniel Borkmann
2016-01-07 13:56 ` Daniel Borkmann
2016-01-07 16:21 ` Nicolas Dichtel [this message]
2016-01-11 16:28 ` Stephen Hemminger
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=568E909E.1080409@6wind.com \
--to=nicolas.dichtel@6wind$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=julien.floret@6wind$(echo .)com \
--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