From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: linux: missing bfq i/o scheduler
Date: Tue, 18 Jun 2019 22:33:11 +0200 [thread overview]
Message-ID: <20190618203311.lQkQSGg19TlfoJsCm9S5eu0n6NuS0ZzkRj6qxMPr-o0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12530@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/12530#issuecomment-503300366
Comment:
The scheduler is now enabled in the kernel configuration for all relevant kernel versions. I did not increase the revision of the package because the builders have been busy all day building kernels because of the SACK security vulnerability and I don't think we can afford another rebuild right now. So the change will only become effective in binary packages once the next version is released and the packages are rebuilt.
prev parent reply other threads:[~2019-06-18 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 17:22 [ISSUE] " voidlinux-github
2019-06-18 20:32 ` [ISSUE] [CLOSED] " voidlinux-github
2019-06-18 20:32 ` voidlinux-github
2019-06-18 20:33 ` voidlinux-github [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190618203311.lQkQSGg19TlfoJsCm9S5eu0n6NuS0ZzkRj6qxMPr-o0@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).