From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] 3.10.34-1 dev build released
Date: Sat, 29 Mar 2014 12:33:16 -0700 [thread overview]
Message-ID: <CAA93jw4y2b0yK27=HJhAeV6QbFeQMR41mKbHAqKhG0QmHYwzGA@mail.gmail.com> (raw)
+ Resync with openwrt
+ update to linux-3.10.34-1
- untested (and I don't have time to test this weekend)
http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.34-1/
I regard the first build in a new kernel series as possibly really unstable.
So if you are happy with 3.10.32-12, stay there and let someone else
take their lumps with this.
There were some fixes for wifi that went into .34 that seem trivial but
might be important, notably the one for WPA.
BTW, I tend to read these religiously when they come out (usually
via an announcement on lwn.net.
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.34
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.33
(also in terms of religion my wednesday evenings are spent with lwn.net)
I have to admit that I enjoyed reading commit:
5a0b9c33b0a361a7b82fc4ae509bfc1df004f2c0
But I note:
I'd rather like to outsource tracking new 3.10 kernel versions to someone
else, to act as a "spotter" - 'oh, that bug looks important to get
fixed in cerowrt.'
In fact, if there is anyone out there crazy enough to read 3.14
commits or lkml or netdev or linux-wireless on a regular basis, speak
up....
I long ago gave up on lkml, basically sort for a very few people on
netdev, and haven't been paying much attention to 3.13+.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2014-03-29 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 19:33 Dave Taht [this message]
2014-03-30 13:37 ` David Personette
2014-03-30 22:01 ` Dave Taht
2014-03-31 1:20 ` Valdis.Kletnieks
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4y2b0yK27=HJhAeV6QbFeQMR41mKbHAqKhG0QmHYwzGA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-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