netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "tip-bot2 for Nick Desaulniers" <tip-bot2@linutronix.de>,
	"Borislav Petkov (AMD)" <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	Nathan Chancellor <nathan@kernel.org>,
	Daniel Kolesa <daniel@octaforge.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Sven Volkinsfeld <thyrc@gmx.net>,
	Nick Desaulniers <ndesaulniers@google.com>,
	x86@kernel.org, "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	torvalds@linux-foundation.org
Subject: Re: [tip: x86/bugs] x86/srso: Fix build breakage with the LLVM linker
Date: Thu, 10 Aug 2023 16:25:24 -0700	[thread overview]
Message-ID: <20230810162524.7c426664@kernel.org> (raw)
In-Reply-To: <169165870802.27769.15353947574704602257.tip-bot2@tip-bot2>

On Thu, 10 Aug 2023 09:11:48 -0000 tip-bot2 for Nick Desaulniers wrote:
> The following commit has been merged into the x86/bugs branch of tip:

Hi folks, is there an ETA on this getting to Linus?
The breakage has propagated to the networking trees, if the fix reaches
Linus soon we'll just hold off on applying stuff and fast forward again.

       reply	other threads:[~2023-08-10 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230809-gds-v1-1-eaac90b0cbcc@google.com>
     [not found] ` <169165870802.27769.15353947574704602257.tip-bot2@tip-bot2>
2023-08-10 23:25   ` Jakub Kicinski [this message]
2023-08-11  0:28     ` [tip: x86/bugs] x86/srso: Fix build breakage with the LLVM linker Jakub Kicinski
2023-08-11  0:37       ` Linus Torvalds
2023-08-11  9:02         ` Borislav Petkov

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=20230810162524.7c426664@kernel.org \
    --to=kuba@kernel.org \
    --cc=bp@alien8.de \
    --cc=daniel@octaforge.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=thyrc@gmx.net \
    --cc=tip-bot2@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).