[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6844e2b-530f-14b2-0ec3-d47574135571@huawei.com>
Date: Mon, 5 Jul 2021 20:06:50 +0800
From: Yunsheng Lin <linyunsheng@...wei.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
CC: <davem@...emloft.net>, <kuba@...nel.org>, <mst@...hat.com>,
<jasowang@...hat.com>, <nickhu@...estech.com>,
<green.hu@...il.com>, <deanbo422@...il.com>,
<akpm@...ux-foundation.org>, <yury.norov@...il.com>,
<ojeda@...nel.org>, <ndesaulniers@...ogle.com>, <joe@...ches.com>,
<linux-kernel@...r.kernel.org>,
<virtualization@...ts.linux-foundation.org>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/2] refactor the ringtest testing for ptr_ring
On 2021/7/5 17:56, Andy Shevchenko wrote:
> On Mon, Jul 05, 2021 at 11:57:33AM +0800, Yunsheng Lin wrote:
>> tools/include/* have a lot of abstract layer for building
>> kernel code from userspace, so reuse or add the abstract
>> layer in tools/include/ to build the ptr_ring for ringtest
>> testing.
>
> ...
>
>> create mode 100644 tools/include/asm/cache.h
>> create mode 100644 tools/include/asm/processor.h
>> create mode 100644 tools/include/generated/autoconf.h
>> create mode 100644 tools/include/linux/align.h
>> create mode 100644 tools/include/linux/cache.h
>> create mode 100644 tools/include/linux/slab.h
>
> Maybe somebody can change this to be able to include in-tree headers directly?
If the above works, maybe the files in tools/include/* is not
necessary any more, just use the in-tree headers to compile
the user space app?
Or I missed something here?
>
> Besides above, had you tested this with `make O=...`?
You are right, the generated/autoconf.h is in another directory
with `make O=...`.
Any nice idea to fix the above problem?
>
Powered by blists - more mailing lists