From: Jiri Kosina <jkosina@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2 0/4] performance walnuts
Date: Fri, 8 Mar 2019 10:15:01 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1903081013560.19912@cbobk.fhfr.pm> (raw)
In-Reply-To: <20190307220648.GA7544@kroah.com>
On Thu, 7 Mar 2019, speck for Greg KH wrote:
> As for 4.4.y, no, I'm not going to do patches for that tree. If people
> really want that, we can work on them after-the-fact on the stable
> mailing list. Hopefully no one is still using 4.4.y on x86 systems
> anymore (except for enterprise kernels of course...)
We're of course :) working on 4.4 backport for our enterprise kernel. I'll
share it here once it's ready before embargo, or stable can pick it up
after we publish it post-CRD.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2019-03-08 9:15 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
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 [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=nycvar.YFH.7.76.1903081013560.19912@cbobk.fhfr.pm \
--to=jkosina@suse.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).