bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: jpoimboe@kernel.org, mingo@redhat.com, tglx@linutronix.de,
	bp@alien8.de, x86@kernel.org, leit@meta.com,
	linux-kernel@vger.kernel.org, pawan.kumar.gupta@linux.intel.com,
	bpf@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v6 00/13] x86/bugs: Add a separate config for each mitigation
Date: Wed, 10 Jan 2024 19:07:48 +0100	[thread overview]
Message-ID: <ZZ7c9EbJ71zU5TOF@gmail.com> (raw)
In-Reply-To: <ZZ6FwMTRppSa2eOG@gmail.com>


* Breno Leitao <leitao@debian.org> wrote:

> > Yeah, so:
> > 
> >  - I took this older series and updated it to current upstream, and made
> >    sure all renames were fully done: there were two new Kconfig option
> >    uses, which I integrated into the series. (Sorry about the delay, holiday & stuff.)
> > 
> >  - I also widened the renames to comments and messages, which were not
> >    always covered.
> > 
> >  - Then I took this cover letter and combined it with a more high level
> >    description of the reasoning behind this series I wrote up, and added it
> >    to patch #1. (see it below.)
> > 
> >  - Then I removed the changelog repetition from the other patches and just
> >    referred them back to patch #1.
> > 
> >  - Then I stuck the resulting updated series into tip:x86/bugs, without the 
> >    last 3 patches that modify behavior.
> 
> Thanks for your work. I am currently reviwing the tip branch and the
> merge seems go so far.
> 
> Regarding the last 3 patches, what are the next steps?

Please resubmit them in a few days (with Josh's Acked-by added and any 
fixes/enhancements done along the way), on top of tip:x86/bugs.

Thanks,

	Ingo

  reply	other threads:[~2024-01-10 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 16:07 [PATCH v6 00/13] x86/bugs: Add a separate config for each mitigation Breno Leitao
2023-11-21 16:07 ` [PATCH v6 05/13] x86/bugs: Rename RETPOLINE to MITIGATION_RETPOLINE Breno Leitao
2023-11-22 15:08   ` Ariel Miculas
2023-11-21 16:07 ` [PATCH v6 06/13] x86/bugs: Rename SLS to CONFIG_MITIGATION_SLS Breno Leitao
2023-11-29  4:42 ` [PATCH v6 00/13] x86/bugs: Add a separate config for each mitigation Josh Poimboeuf
2024-01-10  9:56 ` Ingo Molnar
2024-01-10 11:55   ` Breno Leitao
2024-01-10 18:07     ` Ingo Molnar [this message]
2024-04-30 13:12       ` Breno Leitao

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=ZZ7c9EbJ71zU5TOF@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=leit@meta.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 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 NNTP newsgroup(s).