[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d12dd3ba-8b24-4fcf-8c55-00c765628836@nvidia.com>
Date: Fri, 8 Dec 2023 17:39:06 -0800
From: John Hubbard <jhubbard@...dia.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: David Hildenbrand <david@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Xu <peterx@...hat.com>, Shuah Khan <shuah@...nel.org>,
"Nathan Chancellor" <nathan@...nel.org>, <linux-mm@...ck.org>,
<linux-kselftest@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Muhammad Usama Anjum <usama.anjum@...labora.com>,
Jonathan Corbet <corbet@....net>, <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v3 11/11] selftests: error out if kernel header files are
not yet built
On 12/8/23 14:10, Peter Zijlstra wrote:
> So as David already argued, the current thing does not in fact help with
> b. You just have to install once and the error goes away, then carry
> that tree for a year and you're running old crap again.
>
> My biggest beef with the whole thing is that I simply do not want to use
> 'make headers', it doesn't work for me.
>
> I have a ton of output directories and I don't care to build tools into
> the output dirs, in fact some of them flat out refuse to work that way
> (bpf comes to mind).
Going with that, then, I believe it is best to simply revert commit
9fc96c7c19df ("selftests: error out if kernel header files are not
yet built"). And then follow up with a series of (many) changes to
wean the various selftests off of the kernel headers.
I'll post the revert shortly.
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists