From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Yicong Yang <yangyicong@huawei.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
yangyicong@hisilicon.com, James Clark <james.clark@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ali Saidi <alisaidi@amazon.com>, Leo Yan <leo.yan@linaro.org>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
yangjinqian <yangjinqian1@huawei.com>,
Douglas Anderson <dianders@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf usage of arch/arm64/include/asm/cputype.h
Date: Wed, 18 Jun 2025 10:15:04 -0300 [thread overview]
Message-ID: <aFK72GUlT-EStfU2@x1> (raw)
In-Reply-To: <20250618112440.GC794930@e132581.arm.com>
On Wed, Jun 18, 2025 at 12:24:40PM +0100, Leo Yan wrote:
> On Wed, Jun 18, 2025 at 09:52:53AM +0100, Mark Rutland wrote:
> > If we want to share headers between userspace and kernel, we should
> > refactor those headers such that this is safe by construction.
> > There is no need to update the userspace headers just because the kernel
> > headers have changed, so the simple solution in the short term is to
> > suppress the warning from check-headers.sh.
> Sure, makes sense for me.
>
> @Arnaldo, as Mark suggested, do you want me to send a patch to remove
> cputype.h checking in check-headers.sh or it is fine to keep the warning
> until finish the header refactoring?
It is ok to have the warning, its just this one at this point and it is
serving its purpose.
When the refactoring gets done, it will go away. Think of it as a
reminder :-)
- Arnaldo
next prev parent reply other threads:[~2025-06-18 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aEyGg98z-MkcClXY@x1>
2025-06-16 7:56 ` perf usage of arch/arm64/include/asm/cputype.h Yicong Yang
2025-06-16 9:29 ` James Clark
2025-06-16 9:54 ` Shameerali Kolothum Thodi
2025-06-16 13:07 ` Leo Yan
2025-06-16 15:04 ` Yicong Yang
2025-06-16 16:08 ` Leo Yan
2025-06-16 17:47 ` Mark Rutland
2025-06-17 14:18 ` Leo Yan
2025-06-18 6:47 ` Yicong Yang
2025-06-18 8:52 ` Mark Rutland
2025-06-18 11:24 ` Leo Yan
2025-06-18 11:51 ` Yicong Yang
2025-06-18 13:02 ` Leo Yan
2025-06-18 13:15 ` Arnaldo Carvalho de Melo [this message]
2025-06-18 14:44 ` Leo Yan
2025-06-16 17:41 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aFK72GUlT-EStfU2@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alisaidi@amazon.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=james.morse@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=yangjinqian1@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox