From: Jonathan Morton <chromatix99@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake in userspace
Date: Mon, 18 Apr 2016 15:07:14 +0300 [thread overview]
Message-ID: <8F738ACF-F9CB-4C31-870A-18FB80ADBB48@gmail.com> (raw)
In-Reply-To: <CAGnRvurA1BG2-ruJO+1kLWME6pi43Lot_4GFLbe_BOpJ1eTCSg@mail.gmail.com>
> On 18 Apr, 2016, at 14:40, Henning Rogge <hrogge@gmail.com> wrote:
>
> But the relevant include file does not contain it. Most likely an
> Ubuntu problem.
There seem often to be problems with Ubuntu kernels’ internal APIs not matching their nominal version numbers. I advise keeping a local, manually hacked version of codel5_compat.h, unless someone knows a foolproof way of distinguishing an Ubuntu kernel from a normal one.
- Jonathan Morton
prev parent reply other threads:[~2016-04-18 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 11:02 Henning Rogge
2016-04-15 11:41 ` Jonathan Morton
2016-04-15 13:16 ` Henning Rogge
2016-04-15 13:19 ` Jonathan Morton
2016-04-18 11:17 ` Henning Rogge
2016-04-18 11:40 ` Henning Rogge
2016-04-18 12:07 ` Jonathan Morton [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8F738ACF-F9CB-4C31-870A-18FB80ADBB48@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=hrogge@gmail.com \
/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