From: Ben Hutchings <ben@decadent.org.uk>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: David Miller <davem@davemloft.net>,
eric.dumazet@gmail.com, akpm@linux-foundation.org,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [Bugme-new] [Bug 34322] New: No ECN marking in IPv6
Date: Fri, 13 May 2011 05:04:37 +0100 [thread overview]
Message-ID: <1305259477.4065.405.camel@localhost> (raw)
In-Reply-To: <20110512225458.GA19573@uio.no>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Fri, 2011-05-13 at 00:15 +0100, Steinar H. Gunderson wrote:
> On Thu, May 12, 2011 at 03:52:21PM -0700, David Miller wrote:
> >>> I cooked for you the official patch and made sure it worked with a RED
> >>> ECN setup, and one ipv6 tcp xmit.
> >> Great, thanks :-) This looks good to me.
> > Applied, thanks everyone.
>
> Do you think it would be possible to get it backported to stable kernels?
> (I've been told getting it into the 2.6.32.x series is the easiest way to get
> it into Debian stable, and I guess it should be a candidate.)
If this doesn't apply directly to 2.6.32 then you'll need to prepare the
backport and send it to stable@kernel.org with a reference to the commit
in mainline.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2011-05-13 4:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-34322-10286@https.bugzilla.kernel.org/>
2011-05-05 21:41 ` [Bugme-new] [Bug 34322] New: No ECN marking in IPv6 Andrew Morton
2011-05-06 15:04 ` Eric Dumazet
2011-05-06 17:12 ` Steinar H. Gunderson
2011-05-07 9:44 ` Eric Dumazet
2011-05-07 9:59 ` Steinar H. Gunderson
2011-05-12 22:52 ` David Miller
2011-05-12 22:54 ` Steinar H. Gunderson
2011-05-12 22:58 ` David Miller
2011-05-13 4:04 ` Ben Hutchings [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=1305259477.4065.405.camel@localhost \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sgunderson@bigfoot.com \
--cc=yoshfuji@linux-ipv6.org \
/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).