From: Peter Zijlstra <peterz@infradead.org>
To: "Vineeth Pillai (Google)" <vineeth@bitbyteword.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Joel Fernandes <joel@joelfernandes.org>,
shraash@google.com, marcel.ziswiler@codethink.co.uk,
i.maximets@ovn.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] sched/dlserver: flag to represent active status of dlserver
Date: Fri, 13 Dec 2024 13:51:47 +0100 [thread overview]
Message-ID: <20241213125147.GC35539@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241213032244.877029-1-vineeth@bitbyteword.org>
Thanks, I've invented a Fixes tag for them and stuck them in
queue/sched/urgent for the robot (although I don't expect many
complaints from it).
I'll graduate them to tip/sched/urgent if nothing comes up.
next prev parent reply other threads:[~2024-12-13 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 3:22 [PATCH 1/2] sched/dlserver: flag to represent active status of dlserver Vineeth Pillai (Google)
2024-12-13 3:22 ` [PATCH 2/2] sched/dlserver: fix dlserver time accounting Vineeth Pillai (Google)
2024-12-13 10:10 ` Marcel Ziswiler
2024-12-14 18:36 ` [tip: sched/urgent] sched/dlserver: Fix " tip-bot2 for Vineeth Pillai (Google)
2024-12-13 10:10 ` [PATCH 1/2] sched/dlserver: flag to represent active status of dlserver Marcel Ziswiler
2024-12-13 12:51 ` Peter Zijlstra [this message]
2024-12-13 12:58 ` Ilya Maximets
2024-12-13 14:57 ` Juri Lelli
2024-12-14 18:37 ` [tip: sched/urgent] sched/dlserver: Fix dlserver double enqueue tip-bot2 for Vineeth Pillai (Google)
2024-12-17 16:44 ` [PATCH 1/2] EXP sched/dlserver: flag to represent active status of dlserver Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2024-12-13 3:21 [PATCH 1/2] " Vineeth Pillai (Google)
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=20241213125147.GC35539@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=i.maximets@ovn.org \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@codethink.co.uk \
--cc=mingo@redhat.com \
--cc=shraash@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.