From: Byungchul Park <byungchul.park@lge.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, rostedt@goodmis.org, tglx@linutronix.de,
raistlin@linux.it, linux-kernel@vger.kernel.org,
juri.lelli@gmail.com, bristot@redhat.com, kernel-team@lge.com
Subject: Re: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up
Date: Mon, 26 Feb 2018 16:51:19 +0900 [thread overview]
Message-ID: <c1197c02-2ce5-e2cf-0172-003b7eb9de20@lge.com> (raw)
In-Reply-To: <20180111090716.GV6176@hirez.programming.kicks-ass.net>
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
>
>
> Sorry for the huge delay on this, but I'll have to postpone further.
> Still busy with meltdown/spectre stuff.
Do you have time to see the patch, now that it seems to be managed
to solve those security issues?
--
Thanks,
Byungchul
next prev parent reply other threads:[~2018-02-26 7:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 6:14 [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up Byungchul Park
2018-01-08 6:14 ` [RESEND PATCH v3 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value Byungchul Park
2018-06-01 6:12 ` [RESEND, v3, " Joel Fernandes
2018-06-01 6:18 ` Joel Fernandes
2018-06-01 7:10 ` Byungchul Park
2018-06-01 15:52 ` Joel Fernandes
2018-06-03 5:20 ` Byungchul Park
2018-01-11 9:07 ` [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up Peter Zijlstra
2018-02-09 0:37 ` Byungchul Park
2018-02-26 7:51 ` Byungchul Park [this message]
2018-03-13 5:52 ` Byungchul Park
2018-04-23 7:01 ` Byungchul Park
2018-05-09 6:33 ` Byungchul Park
2018-05-25 5:13 ` Byungchul Park
2018-06-01 3:07 ` Byungchul Park
2018-06-01 6:02 ` Joel Fernandes
2018-06-01 6:30 ` Byungchul Park
-- strict thread matches above, loose matches on Subject: below --
2017-12-28 23:32 Byungchul Park
2017-12-19 1:19 Byungchul Park
2017-12-22 6:53 ` Byungchul Park
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=c1197c02-2ce5-e2cf-0172-003b7eb9de20@lge.com \
--to=byungchul.park@lge.com \
--cc=bristot@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).