From: Alessio Balsini <balsini@android.com>
To: alessio.balsini@gmail.com
Cc: bristot@redhat.com, claudio@evidence.eu.com,
joel@joelfernandes.org, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, luca.abeni@santannapisa.it,
mingo@redhat.com, patrick.bellasi@arm.com, peterz@infradead.org,
tommaso.cucinotta@santannapisa.it
Subject: Re: [RFC PATCH] sched/deadline: sched_getattr() returns absolute dl-task information
Date: Mon, 29 Apr 2019 17:11:34 +0100 [thread overview]
Message-ID: <20190429161134.uvgikvfg7rv2wkff@google.com> (raw)
In-Reply-To: <20180629120947.14579-1-alessio.balsini@gmail.com>
prev parent reply other threads:[~2019-04-29 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 12:09 [RFC PATCH] sched/deadline: sched_getattr() returns absolute dl-task information Alessio Balsini
2018-06-29 18:45 ` Joel Fernandes
2018-07-23 9:49 ` Peter Zijlstra
2018-07-23 12:49 ` Patrick Bellasi
2018-07-23 14:13 ` Peter Zijlstra
2018-07-23 14:31 ` Patrick Bellasi
2019-04-29 16:11 ` Alessio Balsini [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=20190429161134.uvgikvfg7rv2wkff@google.com \
--to=balsini@android.com \
--cc=alessio.balsini@gmail.com \
--cc=bristot@redhat.com \
--cc=claudio@evidence.eu.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=tommaso.cucinotta@santannapisa.it \
/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