From: Jan Beulich <jbeulich@suse.com>
To: Chuck Zmudzinski <brchuckz@netscape.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sean Christopherson <seanjc@google.com>,
xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/PAT: Report PAT on CPUs that support PAT without MTRR
Date: Wed, 13 Jul 2022 07:55:03 +0200 [thread overview]
Message-ID: <09fee965-9cf2-110c-4484-d00bddb6b782@suse.com> (raw)
In-Reply-To: <32c86239-c434-369d-b6a7-f6f88cf5430a@netscape.net>
On 12.07.2022 21:48, Chuck Zmudzinski wrote:
> I will also re-compile and test the new patch before sending
> v2 and unless Jan objects, I should acknowledge Jan as co-author
> of the patch since I will be using parts of his proposed patch
> to fix the "nopat" issue, so I also need to get his sign-off before
> sending v2. Jan, how should I obtain your sign-off?
If you really re-use any meaningful part, I think you could simply
propagate it from the patch I had sent. But I'd expect the pieces
to be too minor to actually warrant that.
Jan
next prev parent reply other threads:[~2022-07-13 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2885cdcaccffd287ef69c7509056ddf183a38a0e.1657647656.git.brchuckz.ref@aol.com>
2022-07-12 18:20 ` Chuck Zmudzinski
2022-07-12 18:27 ` Juergen Gross
2022-07-12 19:18 ` Chuck Zmudzinski
2022-07-12 19:48 ` Chuck Zmudzinski
2022-07-13 5:55 ` Jan Beulich [this message]
2022-07-12 18:36 ` Greg KH
2022-07-12 19:16 ` Chuck Zmudzinski
2022-07-12 19:26 ` Greg KH
2022-07-12 19:57 ` Chuck Zmudzinski
2022-07-13 5:35 ` Greg KH
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=09fee965-9cf2-110c-4484-d00bddb6b782@suse.com \
--to=jbeulich@suse.com \
--cc=bp@alien8.de \
--cc=brchuckz@netscape.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--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
all inboxes | Powered by JetHome®