[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c6f86b4-8151-4bb8-8400-3ea546ca10ac@nvidia.com>
Date: Thu, 13 Jun 2024 14:27:31 -0700
From: John Hubbard <jhubbard@...dia.com>
To: David Hildenbrand <david@...hat.com>, Andrew Morton
<akpm@...ux-foundation.org>, Jeff Xu <jeffxu@...omium.org>, Shuah Khan
<shuah@...nel.org>
CC: Andrei Vagin <avagin@...gle.com>, Axel Rasmussen
<axelrasmussen@...gle.com>, Christian Brauner <brauner@...nel.org>, Kees Cook
<kees@...nel.org>, Kent Overstreet <kent.overstreet@...ux.dev>, "Liam R .
Howlett" <Liam.Howlett@...cle.com>, Muhammad Usama Anjum
<usama.anjum@...labora.com>, Peter Xu <peterx@...hat.com>, Rich Felker
<dalias@...c.org>, <linux-mm@...ck.org>, <linux-kselftest@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] cleanups, fixes, and progress towards avoiding "make
headers"
On 6/12/24 7:11 PM, John Hubbard wrote:
> On 6/12/24 1:24 AM, David Hildenbrand wrote:
>> On 11.06.24 22:54, John Hubbard wrote:
>>> On 6/11/24 2:36 AM, David Hildenbrand wrote:
>>>> On 08.06.24 04:10, John Hubbard wrote:
...
>>> You remembered correctly, but the situation is slighly muddier than
>>> one would prefer. :)
>>
>>
>> Absolutely, and I appreciate that you are trying to improve the situation.
>>
>
> I think the attempts to further tease apart the include headers could
> go into a separate, subsequent series, yes? And let this one go in
> unmolested for now?
On second thought, it is actually much easier than I thought, let me
post a v2 with the unistd.h header fixes, after all.
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists