From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: 2.6.39 + cerowrt
Date: Thu, 30 Jun 2011 03:34:00 -0600 [thread overview]
Message-ID: <BANLkTikq9Xs+cRYrQneueF=+-+-ku6LMQQ@mail.gmail.com> (raw)
At one level, I'm happy.
At another it's now a real blur to me what did and didn't get
backported. I do think there were some good fixes to SFQ that were in
2.6.39 that weren't in 2.6.37.6
And on the gripping hand I'm glad this happened today rather than next week.
doing a new build, ripping out sfb backport, crossing fingers, hoping
for a non-brick...
commit 1c570d4d173fa669caa0d145ac7430d27c33b93e
Author: juhosg <juhosg@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Date: Wed Jun 29 08:57:33 2011 +0000
ar71xx: switch to 2.6.39
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27311
3c298f89-4303-0410-b956-a3cf2f4a3e73
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
reply other threads:[~2011-06-30 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='BANLkTikq9Xs+cRYrQneueF=+-+-ku6LMQQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
/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