From: Frank Horowitz <frank@horow.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Instrumented ATH9K for Crashes?
Date: Fri, 17 Feb 2017 10:47:05 -0500 [thread overview]
Message-ID: <97E1BFD0-7E33-4325-AB97-E92CFF453494@horow.net> (raw)
In-Reply-To: <87y3x53zub.fsf@alrua-karlstad>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Git describe shows v4.10-rc7-1866-g135f8e5 and I’m definitely on the net-next tree. I’m going to try the patch Dave just pointed to to see if it applies cleanly.
Frank
> On Feb 17, 2017, at 4:56 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Dave Taht <dave.taht@gmail.com> writes:
>
>> It is my hope felix squished it last week.
>>
>> https://patchwork.kernel.org/patch/9568369/
>
> That is a fix to the airtime fairness patch, though, which is not in
> 4.10. But if the kernel is from net-next, it's probably not actually
> 4.10; Frank, did you get that from git describe? Because then it's
> probably not 4.10-rc7, but 4.10-rc7+something, which is different (yeah,
> git describe is annoying that way).
>
> As far as instrumenting a box for capturing logs, I ended up using an
> old-fashioned serial cable to another machine in my test setup...
>
> -Toke
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2017-02-17 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 3:18 Frank Horowitz
2017-02-17 3:50 ` Dave Taht
2017-02-17 9:56 ` Toke Høiland-Jørgensen
2017-02-17 15:47 ` Frank Horowitz [this message]
2017-02-17 16:22 ` Toke Høiland-Jørgensen
2017-02-17 16:24 ` Frank Horowitz
2017-02-19 13:58 ` Dave Taht
2017-02-19 14:27 ` Frank Horowitz
2017-02-19 14:45 ` Dave Taht
2017-02-19 14:48 ` Frank Horowitz
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97E1BFD0-7E33-4325-AB97-E92CFF453494@horow.net \
--to=frank@horow.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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