From: Matt Taggart <matt@lackof.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] ar71xx CC builds and tc
Date: Thu, 13 Aug 2015 15:50:46 -0700 [thread overview]
Message-ID: <20150813225046.81E9B203@taggart.lackof.org> (raw)
Hi,
I have installed a bunch of wndr3800's in the last few days with CC and
noticed a couple things:
1) sometime around Aug 11 the ar71xx-generic builds jumped from having a
date of mid july and using a 3.18 kernel, to having a Aug 11 date and
4.1.4 kernel. I guess builds weren't working and then got fixed? Anyway
maybe a good time for people to test newer builds.
2) CC doesn't seem to include tc by default now, so when I installed
luci-app-sqm (which pulls in sqm-scripts) things weren't working
correctly. After I installed tc then it started working. Toke, maybe
you need to have sqm-scripts start depending on tc?
Thanks,
--
Matt Taggart
matt@lackof.org
next reply other threads:[~2015-08-13 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 22:50 Matt Taggart [this message]
2015-08-13 23:01 ` Toke Høiland-Jørgensen
2015-08-15 20:15 ` Maciej Soltysiak
2015-08-16 10:01 ` Toke Høiland-Jørgensen
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=20150813225046.81E9B203@taggart.lackof.org \
--to=matt@lackof.org \
--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