All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mitchell Levy <levymitchell0@gmail.com>
Cc: Mitchell Levy via B4 Relay
	<devnull+levymitchell0.gmail.com@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	stable@vger.kernel.org, Borislav Petkov <bp@suse.de>,
	linux-kernel@vger.kernel.org, Dave Hansen <dave.hansen@intel.com>
Subject: Re: [PATCH v2] x86/fpu: Avoid writing LBR bit to IA32_XSS unless supported
Date: Sun, 11 Aug 2024 09:50:46 +0200	[thread overview]
Message-ID: <87r0avsdk9.ffs@tglx> (raw)
In-Reply-To: <66b80624.050a0220.39b486.4736@mx.google.com>

On Sat, Aug 10 2024 at 17:30, Mitchell Levy wrote:
> On Sun, Aug 11, 2024 at 01:08:18AM +0200, Thomas Gleixner wrote:
>> May I ask you to read Documentation/process/ ?
> Yes, I have now more thoroughly covered these docs. On second look, it
> appears there's no Signed-off-by in your reply to my v1. I can send the
> patch with you properly listed as the author and the proper
> Signed-off-by lines if I have your permission to add your signoff.
> Alternatively, feel free to reuse part/all of my commit message if you'd
> rather submit the patch directly; it's quite understandable if you feel
> unenthusiastic about me being involved with code you've authored.

Don't worry. Just add: Suggested-by: Thomas Gleixner <tglx@linutronix.de>

and be done with it.

Thanks,

        tglx

      reply	other threads:[~2024-08-11  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 20:53 [PATCH v2] x86/fpu: Avoid writing LBR bit to IA32_XSS unless supported Mitchell Levy
2024-08-09 20:53 ` Mitchell Levy via B4 Relay
2024-08-10 23:08 ` Thomas Gleixner
2024-08-11  0:30   ` Mitchell Levy
2024-08-11  7:50     ` Thomas Gleixner [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=87r0avsdk9.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=devnull+levymitchell0.gmail.com@kernel.org \
    --cc=hpa@zytor.com \
    --cc=kan.liang@linux.intel.com \
    --cc=levymitchell0@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --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 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.