From: Frank Horowitz <frank@horow.net>
To: toke@toke.dk
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] ATH9K Airtime fairness in git?
Date: Mon, 2 Jan 2017 11:14:13 -0500 [thread overview]
Message-ID: <DF426D6C-8762-404C-8B34-6CF1C17E9A63@horow.net> (raw)
Hi Toke (et al.)
First off, thanks for all of your hard work on this!
I’m attempting to patch a relatively mainline kernel tree with your ath9k patches — mostly so I can have those patches and BBR in one box. I’m having some issues applying your LEDE patch to a 4.9 kernel, and want to try with git’s help from an ancestral tree. Do you have an accessible git repository with your patch integrated into kernel 4.4 or newer (as opposed to the patch itself in the LEDE tree)?
Many Thanks (and Happy New Year to all!),
Frank Horowitz
next reply other threads:[~2017-01-02 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 16:14 Frank Horowitz [this message]
2017-01-02 16:33 ` Toke Høiland-Jørgensen
2017-01-02 16:50 ` Dave Taht
2017-01-02 17:08 ` Loganaden Velvindron
2017-01-02 17:17 ` Dave Taht
2017-01-02 22:55 ` Dave Taht
2017-01-02 22:58 ` Jonathan Morton
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=DF426D6C-8762-404C-8B34-6CF1C17E9A63@horow.net \
--to=frank@horow.net \
--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