Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Robert Gill <rtgill82@gmail.com>,
	Jari Ruusu <jariruusu@protonmail.com>,
	Brian Gerst <brgerst@gmail.com>,
	antonio.gomez.iglesias@linux.intel.com,
	daniel.sneddon@linux.intel.com, stable@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH v7 0/3] Fix dosemu vm86() fault
Date: Tue, 8 Oct 2024 15:48:33 -0700	[thread overview]
Message-ID: <212478a0-ab8a-4ed7-8dfb-600f9d81e7ba@intel.com> (raw)
In-Reply-To: <bd933e11-7836-462f-9b6b-5172301f188b@leemhuis.info>

On 10/8/24 06:52, Thorsten Leemhuis wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> for once, to make this easily accessible to everyone.
> 
> Is there hope that patches like these makes it to mainline any time
> soon?

Unless it breaks something again:

> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=785bf1ab58aa1f89a5dfcb17b682b7089d69c34f

;)

> This yet again makes me wonder if some "[regression fix]" in the subject
> or "CC: regressions@lists.linux.dev" in the patches would help to make
> the regression aspect obvious to everyone involved. But it would create
> yet another small bit of overhead

In this case, not really.  This was a typical email screwup where I
didn't pick up that there was an updated patch that got appended to a
reply among the normal email noise.

We've been poking at this pretty regularly since getting back from Plumbers.

  reply	other threads:[~2024-10-08 22:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 22:25 [PATCH v7 0/3] Fix dosemu vm86() fault Pawan Gupta
2024-09-25 22:25 ` [PATCH v7 1/3] x86/entry_32: Do not clobber user EFLAGS.ZF Pawan Gupta
2024-09-25 22:25 ` [PATCH v7 2/3] x86/entry_32: Clear CPU buffers after register restore in NMI return Pawan Gupta
2024-09-25 22:25 ` [PATCH v7 3/3] x86/bugs: Use code segment selector for VERW operand Pawan Gupta
2024-09-25 23:29   ` Andrew Cooper
2024-09-25 23:46     ` Pawan Gupta
2024-09-26  0:17       ` Pawan Gupta
2024-09-26  0:32         ` Andrew Cooper
2024-09-26  1:04           ` Pawan Gupta
2024-09-26 14:52         ` Uros Bizjak
2024-09-26 16:10           ` Pawan Gupta
2024-09-26 16:28             ` Andrew Cooper
2024-09-26 16:56               ` Pawan Gupta
2024-09-26 17:01                 ` Andrew Cooper
2024-10-08 13:52 ` [PATCH v7 0/3] Fix dosemu vm86() fault Thorsten Leemhuis
2024-10-08 22:48   ` Dave Hansen [this message]
2024-10-09  8:50     ` Linux regression tracking (Thorsten Leemhuis)

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=212478a0-ab8a-4ed7-8dfb-600f9d81e7ba@intel.com \
    --to=dave.hansen@intel.com \
    --cc=antonio.gomez.iglesias@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=daniel.sneddon@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jariruusu@protonmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=rtgill82@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox