From: Borislav Petkov <bp@alien8.de>
To: Chuck Zmudzinski <brchuckz@netscape.net>
Cc: Juergen Gross <jgross@suse.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
regressions@lists.linux.dev
Subject: Re: PING [PATCH 3/3] x86: decouple pat and mtrr handling
Date: Sat, 13 Aug 2022 19:20:33 +0200 [thread overview]
Message-ID: <YvfdYS81vU66tQSs@zn.tnic> (raw)
In-Reply-To: <d838264a-bcd0-29e2-3b23-5427ee0ee041@netscape.net>
On Sat, Aug 13, 2022 at 12:56:44PM -0400, Chuck Zmudzinski wrote:
> Why has Juergen not at least responded in some way to the
> comments that Boris has made here? Why has Boris not
> pinged Juergen by now,
How about: it is summer here and people usually take their vacations
during that time and everything takes a bit longer than usual?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-08-13 17:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 14:25 [PATCH 0/3] x86: make pat and mtrr independent from each other Juergen Gross
2022-07-15 14:25 ` [PATCH 1/3] x86: move some code out of arch/x86/kernel/cpu/mtrr Juergen Gross
2022-07-18 12:20 ` Borislav Petkov
2022-07-15 14:25 ` [PATCH 2/3] x86: add wrapper functions for mtrr functions handling also pat Juergen Gross
2022-07-15 16:41 ` Rafael J. Wysocki
2022-07-19 10:47 ` Borislav Petkov
2022-07-15 14:25 ` [PATCH 3/3] x86: decouple pat and mtrr handling Juergen Gross
2022-07-19 15:15 ` Borislav Petkov
2022-08-13 16:56 ` PING " Chuck Zmudzinski
2022-08-13 17:20 ` Borislav Petkov [this message]
2022-08-13 21:40 ` Chuck Zmudzinski
2022-08-13 21:48 ` Borislav Petkov
2022-08-13 22:41 ` Chuck Zmudzinski
2022-08-16 18:31 ` Chuck Zmudzinski
2022-08-17 9:17 ` Juergen Gross
2022-07-20 1:12 ` Chuck Zmudzinski
2022-07-16 11:32 ` [PATCH 0/3] x86: make pat and mtrr independent from each other Chuck Zmudzinski
2022-07-16 11:42 ` Borislav Petkov
2022-07-17 4:06 ` Chuck Zmudzinski
2022-07-16 12:01 ` Chuck Zmudzinski
2022-07-17 7:55 ` Thorsten Leemhuis
2022-07-18 11:32 ` Chuck Zmudzinski
2022-07-19 13:16 ` Chuck Zmudzinski
2022-08-13 16:56 ` Chuck Zmudzinski
2022-08-14 7:42 ` Chuck Zmudzinski
2022-08-14 8:08 ` Juergen Gross
2022-08-15 3:23 ` Chuck Zmudzinski
2022-08-15 16:56 ` Chuck Zmudzinski
2022-08-15 18:00 ` Thorsten Leemhuis
2022-08-15 18:17 ` Chuck Zmudzinski
2022-08-16 14:41 ` Thorsten Leemhuis
2022-08-16 16:16 ` Chuck Zmudzinski
2022-08-16 16:53 ` Thorsten Leemhuis
2022-08-16 17:28 ` Chuck Zmudzinski
2022-08-18 18:54 ` Chuck Zmudzinski
2022-08-14 9:19 ` Chuck Zmudzinski
2022-08-14 9:50 ` Greg KH
2022-08-14 12:08 ` Chuck Zmudzinski
2022-08-14 13:01 ` Greg KH
2022-08-14 16:03 ` Chuck Zmudzinski
2022-08-14 19:52 ` Chuck Zmudzinski
2022-08-15 16:04 ` Chuck Zmudzinski
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=YvfdYS81vU66tQSs@zn.tnic \
--to=bp@alien8.de \
--cc=boris.ostrovsky@oracle.com \
--cc=brchuckz@netscape.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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