From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Vineeth Remanan Pillai <vineeth@bitbyteword.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Fernandes <joel@joelfernandes.org>,
youssefesmat@google.com,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
luca abeni <luca.abeni@santannapisa.it>
Subject: Re: [PATCH v4 1/2] sched/deadline: Fix bandwidth reclaim equation in GRUB
Date: Tue, 30 May 2023 15:11:18 +0200 [thread overview]
Message-ID: <e9ea284d-3a8b-b9ef-d179-b67628771bf4@redhat.com> (raw)
In-Reply-To: <CAO7JXPgf9ffVQ3n9iD8-1abuDSAZHWAZmz56BmM68uJZ7uy+Uw@mail.gmail.com>
On 5/26/23 18:15, Vineeth Remanan Pillai wrote:
> I have just sent the fix as a reply to the initial patch. I shall send a
> v5 if needed. Please let me know.
Please, send a v5... so we avoid mixing up patches on testing.
-- Daniel
next prev parent reply other threads:[~2023-05-30 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 14:55 [PATCH v4 1/2] sched/deadline: Fix bandwidth reclaim equation in GRUB Vineeth Pillai
2023-05-26 14:55 ` [PATCH v4 2/2] sched/deadline: Update GRUB description in the documentation Vineeth Pillai
2023-05-26 16:10 ` Vineeth Pillai
2023-05-26 15:29 ` [PATCH v4 1/2] sched/deadline: Fix bandwidth reclaim equation in GRUB luca abeni
2023-05-26 15:55 ` Vineeth Remanan Pillai
2023-05-26 15:58 ` Vineeth Remanan Pillai
2023-05-26 16:15 ` Vineeth Remanan Pillai
2023-05-30 13:11 ` Daniel Bristot de Oliveira [this message]
2023-05-30 13:22 ` Vineeth Remanan Pillai
2023-05-26 16:09 ` Vineeth Pillai
2023-06-02 18:40 ` Joel Fernandes
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=e9ea284d-3a8b-b9ef-d179-b67628771bf4@redhat.com \
--to=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.org \
--cc=vschneid@redhat.com \
--cc=youssefesmat@google.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