Archive-only list for patches
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, x86@kernel.org, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	patches@lists.linux.dev
Subject: Re: [PATCH] x86/tools: objdump_reformat.awk: Skip bad instructions from llvm-objdump
Date: Wed, 3 Jan 2024 13:55:06 -0700	[thread overview]
Message-ID: <20240103205506.GA152662@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20240103181852.GDZZWlDJMVvqAZdpfV@fat_crate.local>

On Wed, Jan 03, 2024 at 07:18:52PM +0100, Borislav Petkov wrote:
> On Wed, Jan 03, 2024 at 11:15:42AM -0700, Nathan Chancellor wrote:
> > Ping? I am still seeing this issue.
> 
> Does this need a Fixes tag and needs to go to Linus now or are you fine
> with 6.8-rc0?

This is only needed due to the recent changes from Sam and myself in
x86/build, so no need to rush it to Linus. I just wanted to make sure it
was not lost before the chaos of the merge window.

Cheers,
Nathan

  reply	other threads:[~2024-01-03 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 19:53 [PATCH] x86/tools: objdump_reformat.awk: Skip bad instructions from llvm-objdump Nathan Chancellor
2024-01-03 18:15 ` Nathan Chancellor
2024-01-03 18:18   ` Borislav Petkov
2024-01-03 20:55     ` Nathan Chancellor [this message]
2024-01-03 21:26       ` Borislav Petkov
2024-01-03 21:48         ` Nathan Chancellor
2024-01-03 21:51           ` Nathan Chancellor
2024-01-04  8:58             ` 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=20240103205506.GA152662@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=patches@lists.linux.dev \
    --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