From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Vineeth Pillai <vineeth@bitbyteword.org>
Cc: luca.abeni@santannapisa.it, Juri Lelli <juri.lelli@redhat.com>,
Daniel Bristot de Oliveira <bristot@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>,
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-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Documentation: sched/deadline: Update GRUB description
Date: Fri, 12 May 2023 14:34:43 +0700 [thread overview]
Message-ID: <ZF3sE5XJATIgoTUM@debian.me> (raw)
In-Reply-To: <20230511014625.3443409-2-vineeth@bitbyteword.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On Wed, May 10, 2023 at 09:46:25PM -0400, Vineeth Pillai wrote:
> Update the details of GRUB to reflect the updated logic.
>
> Signed-off-by: Vineeth Pillai (Google) <vineeth@bitbyteword.org>
You seems forgetting my Reviewed-by: from v1 [1], so I give it again:
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks.
[1]: https://lore.kernel.org/linux-doc/b97d63e4-0ff7-720b-30d7-ad27611e9a8c@gmail.com/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-12 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 1:46 [PATCH v2 1/2] sched/deadline: Improve reclaim bandwidth accuracy for GRUB Vineeth Pillai
2023-05-11 1:46 ` [PATCH v2 2/2] Documentation: sched/deadline: Update GRUB description Vineeth Pillai
2023-05-12 7:34 ` Bagas Sanjaya [this message]
2023-05-11 6:19 ` [PATCH v2 1/2] sched/deadline: Improve reclaim bandwidth accuracy for GRUB Joel Fernandes
2023-05-11 18:55 ` Vineeth Remanan Pillai
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=ZF3sE5XJATIgoTUM@debian.me \
--to=bagasdotme@gmail.com \
--cc=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=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 \
/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).