From: Nelson D'Souza <nelson.dsouza@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2 0/4] performance walnuts
Date: Tue, 5 Mar 2019 14:33:01 -0800 [thread overview]
Message-ID: <f5ec5c2e-eae9-5fc9-6cb3-350dda8904fd@linux.intel.com> (raw)
In-Reply-To: <CAHk-=wjvUDKMgPUbvUqoeHgqjYDh0Y-8idByH0a3UcDjm5E8Nw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
March 12th.
On 3/5/19 2:19 PM, speck for Linus Torvalds wrote:
> On Tue, Mar 5, 2019 at 1:29 PM speck for Peter Zijlstra
> <speck@linutronix.de> wrote:
>>
>> Apparently the intent is to have these patches magically appears in source
>> repos on the 12th.
>
> Which 12th?
>
> I've lost sight of the dates once more. May 14th is still presumably
> MDS one. The walnut one is when?
>
> Linus
>
next prev parent reply other threads:[~2019-03-05 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 21:23 [MODERATED] [PATCH v2 0/4] performance walnuts Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 1/4] perf/x86/intel: Make cpuc allocations consistent Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 2/4] perf/x86/intel: Generalize dynamic constraint creation Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 3/4] x86: Add TSX Force Abort CPUID/MSR Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 4/4] perf/x86/intel: Implement support for TSX Force Abort Peter Zijlstra
2019-03-05 22:19 ` [MODERATED] Re: [PATCH v2 0/4] performance walnuts Linus Torvalds
2019-03-05 22:26 ` Jiri Kosina
2019-03-05 22:33 ` Nelson D'Souza [this message]
2019-03-06 9:23 ` Thomas Gleixner
2019-03-06 11:56 ` [MODERATED] " Greg KH
2019-03-06 13:02 ` David Woodhouse
2019-03-06 18:08 ` Greg KH
2019-03-06 18:32 ` Mark Hatle
2019-03-07 14:12 ` Greg KH
2019-03-07 17:42 ` Mark Hatle
2019-03-07 20:07 ` Thomas Gleixner
2019-03-07 14:13 ` [MODERATED] " Greg KH
2019-03-07 21:42 ` mark gross
2019-03-07 22:06 ` Greg KH
2019-03-08 9:15 ` Jiri Kosina
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=f5ec5c2e-eae9-5fc9-6cb3-350dda8904fd@linux.intel.com \
--to=nelson.dsouza@linux.intel.com \
--cc=speck@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 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.