From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 3BA2921F1A6 for ; Sun, 30 Mar 2014 06:38:11 -0700 (PDT) Received: by mail-yh0-f41.google.com with SMTP id v1so6669301yhn.14 for ; Sun, 30 Mar 2014 06:38:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=DuzY5kVxH88bIZvw10/Ot5bxRHSYg81rc8podGw4KuQ=; b=k0Jbik6sVKE4vL2mNs32Bra76tpwWHz+U4OCZHj8w9sylJl0SlO7BbUkzQimpBngrV /zTlOYh2qfpPOoMez+rt8hLqn4rdcHkMqxh+K+jFOYAb5oAUuYz0tGBjn1H2raN3NBgu LINl+PCCCLH7mcqwZfrHyNwIkwEVLzfBF/6XqBtMRE8PSwNQ1lriCZJkfaSJL0K99Dj6 uzEvPvNfY+ot0LDhNqXrnM7ymUHpC+iYMlZ9kRA7Rnvic0NA8p5440xgRZEbYuKrWw+L 7a1p++Ci/ao1dN2vSzes0zXi/L5yL5jOLv6kTqyKmYpQIxvSxfV1c4VplLIBukFe+Zsk 76bA== X-Received: by 10.236.19.99 with SMTP id m63mr454129yhm.134.1396186689895; Sun, 30 Mar 2014 06:38:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.47.78 with HTTP; Sun, 30 Mar 2014 06:37:49 -0700 (PDT) In-Reply-To: References: From: David Personette Date: Sun, 30 Mar 2014 09:37:49 -0400 Message-ID: To: Dave Taht Content-Type: multipart/alternative; boundary=089e01634dd4b1020904f5d30b22 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] 3.10.34-1 dev build released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2014 13:38:11 -0000 --089e01634dd4b1020904f5d30b22 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've got about 20 hours of uptime now, no issues to report. --=20 David P. On Sat, Mar 29, 2014 at 3:33 PM, Dave Taht wrote: > + 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=C3=A4ht > > Fixing bufferbloat with cerowrt: > http://www.teklibre.com/cerowrt/subscribe.html > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --089e01634dd4b1020904f5d30b22 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've got about 20 hours of uptime now, no issues to re= port.

--
Davi= d P.



On Sat, Mar 29, 2014 at 3:33 PM, Dav= e Taht <dave.taht@gmail.com> wrote:
+ 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.1= 0.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 someo= ne
else, to act as a "spotter" - 'oh, that bug looks important t= o 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=C3=A4ht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

--089e01634dd4b1020904f5d30b22--