[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <212478a0-ab8a-4ed7-8dfb-600f9d81e7ba@intel.com>
Date: Tue, 8 Oct 2024 15:48:33 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Thorsten Leemhuis <regressions@...mhuis.info>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
Robert Gill <rtgill82@...il.com>, Jari Ruusu <jariruusu@...tonmail.com>,
Brian Gerst <brgerst@...il.com>, antonio.gomez.iglesias@...ux.intel.com,
daniel.sneddon@...ux.intel.com, stable@...r.kernel.org,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH v7 0/3] Fix dosemu vm86() fault
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@...ts.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.
Powered by blists - more mailing lists