Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] CAKE build failure on Linux 4.2.2
Date: Thu, 08 Oct 2015 16:43:12 +0200	[thread overview]
Message-ID: <87pp0pxvy7.fsf@toke.dk> (raw)
In-Reply-To: <9045ABF0-BE8F-4D2E-90F0-5AA844445220@gmail.com> (Jonathan Morton's message of "Thu, 8 Oct 2015 17:20:19 +0300")

Jonathan Morton <chromatix99@gmail.com> writes:

> So they’ve removed the old API while the new one still isn’t even
> halfway stable?  Wonderful.  Just when I thought I’d understood how it
> worked.

There's a reason the kernel people are adamant that they don't consider
internal APIs stable... ;)

-Toke

  parent reply	other threads:[~2015-10-08 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08  6:57 Loganaden Velvindron
2015-10-08 12:49 ` Loganaden Velvindron
2015-10-08 14:20 ` Jonathan Morton
2015-10-08 14:27   ` Loganaden Velvindron
2015-10-08 14:43   ` Toke Høiland-Jørgensen [this message]
2015-10-08 15:47   ` Loganaden Velvindron

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=87pp0pxvy7.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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