[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231219020507.cknqkwp2l5ivnrf7@moria.home.lan>
Date: Mon, 18 Dec 2023 21:05:07 -0500
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Sohil Mehta <sohil.mehta@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, X86-kernel <x86@...nel.org>,
tglx@...utronix.de, tj@...nel.org, peterz@...radead.org,
mathieu.desnoyers@...icios.com, paulmck@...nel.org,
keescook@...omium.org, dave.hansen@...ux.intel.com,
mingo@...hat.com, will@...nel.org, longman@...hat.com,
boqun.feng@...il.com, brauner@...nel.org
Subject: Re: [PATCH 02/50] x86/kernel/fpu/bugs.c: fix missing include
On Mon, Dec 18, 2023 at 04:38:33PM +0530, Sohil Mehta wrote:
> For the x86 patches [2-5/50], should the patch subject be a bit more
> generic rather than having the full file name listed.
>
> For example, this patch could be "x86/fpu: Fix missing include".
In the latest version of the patchset I've just rolled all of the
arch/x86 missing includes into one patch.
Powered by blists - more mailing lists