[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250618144414.GF794930@e132581.arm.com>
Date: Wed, 18 Jun 2025 15:44:14 +0100
From: Leo Yan <leo.yan@....com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Yicong Yang <yangyicong@...wei.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com>,
yangyicong@...ilicon.com, James Clark <james.clark@...aro.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
Ali Saidi <alisaidi@...zon.com>, Leo Yan <leo.yan@...aro.org>,
Will Deacon <will@...nel.org>, James Morse <james.morse@....com>,
Catalin Marinas <catalin.marinas@....com>,
yangjinqian <yangjinqian1@...wei.com>,
Douglas Anderson <dianders@...omium.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Ian Rogers <irogers@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Kan Liang <kan.liang@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: perf usage of arch/arm64/include/asm/cputype.h
On Wed, Jun 18, 2025 at 10:15:04AM -0300, Arnaldo Carvalho de Melo wrote:
[...]
> > @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 :-)
Fair point. Thanks for confirmation!
Powered by blists - more mailing lists