Util-Linux Archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Thijs Raymakers <thijs@raymakers.nl>
Cc: thomas@t-8ch.de, util-linux@vger.kernel.org,
	Phil Auld <pauld@redhat.com>
Subject: Re: [PATCH v12] coresched: Manage core scheduling cookies for tasks
Date: Fri, 26 Apr 2024 09:59:53 +0200	[thread overview]
Message-ID: <20240426075953.3zpdrcjgq76dfmz4@ws.net.home> (raw)
In-Reply-To: <20240425162226.130639-1-thijs@raymakers.nl>

On Thu, Apr 25, 2024 at 06:22:25PM +0200, Thijs Raymakers wrote:
> I agree, it would be better to handle it there. The error message "No
> device available" you would get otherwise is a bit cryptic so this
> is an improvement.
> 
> I've removed the ts_skip and added the case there.

PR updated https://github.com/util-linux/util-linux/pull/2990

    Karel
-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com


  reply	other threads:[~2024-04-26  8:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 17:10 [PATCH RFC] coresched: Manage core scheduling cookies for tasks Thijs Raymakers
2024-03-24 20:07 ` Karel Zak
2024-03-26 14:41   ` Phil Auld
2024-03-26 14:45     ` Phil Auld
2024-03-26 17:49     ` [PATCH 0/1] " Thijs Raymakers
2024-03-26 18:13       ` Phil Auld
2024-03-27 12:43         ` [PATCH v2 " Thijs Raymakers
2024-03-27 13:21           ` Phil Auld
2024-03-27 14:18             ` Phil Auld
2024-03-27 15:30               ` [PATCH v3] " Thijs Raymakers
2024-04-01 17:18                 ` Thomas Weißschuh
2024-04-04 22:03                   ` [PATCH v4] " Thijs Raymakers
2024-04-05  6:26                     ` Thomas Weißschuh
2024-04-05 14:14                       ` Phil Auld
2024-04-08 21:16                         ` [PATCH v5] " Thijs Raymakers
2024-04-09  6:12                           ` Thomas Weißschuh
2024-04-09 11:55                             ` [PATCH v6] " Thijs Raymakers
2024-04-09 13:44                               ` Karel Zak
2024-04-09 14:12                                 ` Phil Auld
2024-04-10 21:11                                 ` [PATCH v7] " Thijs Raymakers
2024-04-10 22:15                                   ` Phil Auld
2024-04-11 11:02                                     ` [PATCH v8] " Thijs Raymakers
2024-04-11 13:46                                       ` Phil Auld
2024-04-17 10:31                                         ` Karel Zak
2024-04-17 11:39                                           ` [PATCH v9] " Thijs Raymakers
2024-04-23  9:27                                             ` Karel Zak
2024-04-23 10:19                                             ` Thomas Weißschuh
2024-04-23 11:12                                               ` [PATCH v10] " Thijs Raymakers
2024-04-25 15:36                                                 ` [PATCH v11] " Thijs Raymakers
2024-04-25 15:51                                                   ` Thomas Weißschuh
2024-04-25 16:22                                                     ` [PATCH v12] " Thijs Raymakers
2024-04-26  7:59                                                       ` Karel Zak [this message]
2024-04-26 18:03                                                       ` Thomas Weißschuh
2024-04-29  8:28                                                         ` Karel Zak
2024-04-17 12:27                                           ` [PATCH v8] " Phil Auld
2024-03-27 12:43         ` [PATCH v2 1/1] " Thijs Raymakers
2024-03-27 14:09           ` Phil Auld
2024-03-26 19:09       ` [PATCH 0/1] " Phil Auld
2024-03-26 19:26         ` Thijs Raymakers
2024-03-26 20:16           ` Phil Auld
2024-03-26 20:17             ` Phil Auld
2024-03-26 17:49     ` [PATCH 1/1] " Thijs Raymakers

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=20240426075953.3zpdrcjgq76dfmz4@ws.net.home \
    --to=kzak@redhat.com \
    --cc=pauld@redhat.com \
    --cc=thijs@raymakers.nl \
    --cc=thomas@t-8ch.de \
    --cc=util-linux@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).