From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "janusz.krzysztofik@linux.intel.com"
<janusz.krzysztofik@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>
Cc: "Gross, Jurgen" <jgross@suse.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Marczykowski, Marek" <marmarek@invisiblethingslab.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [Intel-gfx] [PATCH v3 RESEND] x86/mm: Fix PAT bit missing from page protection modify mask
Date: Mon, 17 Jul 2023 21:25:52 +0000 [thread overview]
Message-ID: <379e34f0065552384a2dea12d1726c6727763b8a.camel@intel.com> (raw)
In-Reply-To: <7545651.EvYhyI6sBW@jkrzyszt-mobl2.ger.corp.intel.com>
On Mon, 2023-07-17 at 11:45 +0200, Janusz Krzysztofik wrote:
> I could add your comment and resubmit, but my experience from
> communication
> with audience of this patch tells me that silence means rather no
> acceptance.
I don't think adding a comment to explain tricky hidden details would
typically be controversial. I'd say to comment both if there are more.
But I'll leave you to it.
prev parent reply other threads:[~2023-07-17 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:36 [Intel-gfx] [PATCH v3 RESEND] x86/mm: Fix PAT bit missing from page protection modify mask Janusz Krzysztofik
2023-07-10 8:05 ` Borislav Petkov
2023-07-17 9:42 ` Janusz Krzysztofik
2023-07-10 11:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for x86/mm: Fix PAT bit missing from page protection modify mask (rev4) Patchwork
2023-07-10 12:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-10 14:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-10 17:58 ` [Intel-gfx] [PATCH v3 RESEND] x86/mm: Fix PAT bit missing from page protection modify mask Edgecombe, Rick P
2023-07-17 9:45 ` Janusz Krzysztofik
2023-07-17 21:25 ` Edgecombe, Rick P [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=379e34f0065552384a2dea12d1726c6727763b8a.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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