From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] check_headers.sh with hunk exceptions (lib/list_sort.c tools/ copy)
Date: Thu, 3 Oct 2024 01:21:02 +0800 [thread overview]
Message-ID: <Zv2A/npbGyP2SlKV@visitorckw-System-Product-Name> (raw)
In-Reply-To: <20240930202136.16904-1-acme@kernel.org>
On Mon, Sep 30, 2024 at 05:21:34PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Hi,
>
> Please take a look, as per tools/include/uapi/README we carry
> copies of kernel files for various reasons and check when it drifts, in
> this case we need another way to accept diffs while checking, its all
> spelled out in the individual patches, please ack.
>
> - Arnaldo
>
> Arnaldo Carvalho de Melo (2):
> tools check_headers.sh: Add check variant that excludes some hunks
> perf tools: Cope with differences for lib/list_sort.c copy from the kernel
>
LGTM. For the series:
Acked-by: Kuan-Wei Chiu <visitorckw@gmail.com>
While reviewing the patches, I noticed that there was already a
difference between lib/list_sort.c and tools/lib/list_sort.c regarding
an additional #include <linux/bug.h>. This prompted me to investigate
the reason for this discrepancy. From what I can see, both files only
seem to require only three headers:
#include <linux/compiler.h> /* for likely() macro */
#include <linux/export.h> /* for EXPORT_SYMBOL() macro */
#include <linux/list_sort.h> /* for list_sort() and linux/types.h */
I'll check the git history and run build tests to confirm. If only
these headers are needed, I'll submit a cleanup patch.
Regards,
Kuan-Wei
> .../check-header_ignore_hunks/lib/list_sort.c | 31 +++++++++++++++++++
> tools/perf/check-headers.sh | 29 ++++++++++++++++-
> 2 files changed, 59 insertions(+), 1 deletion(-)
> create mode 100644 tools/perf/check-header_ignore_hunks/lib/list_sort.c
>
> --
> 2.46.0
>
next prev parent reply other threads:[~2024-10-02 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 20:21 [PATCH 0/2] check_headers.sh with hunk exceptions (lib/list_sort.c tools/ copy) Arnaldo Carvalho de Melo
2024-09-30 20:21 ` [PATCH 1/2] tools check_headers.sh: Add check variant that excludes some hunks Arnaldo Carvalho de Melo
2024-09-30 20:21 ` [PATCH 2/2] perf tools: Cope with differences for lib/list_sort.c copy from the kernel Arnaldo Carvalho de Melo
2024-10-01 1:56 ` Namhyung Kim
2024-10-02 17:54 ` Arnaldo Carvalho de Melo
2024-10-02 18:23 ` Namhyung Kim
2024-10-02 17:21 ` Kuan-Wei Chiu [this message]
2024-10-02 17:29 ` [PATCH 0/2] check_headers.sh with hunk exceptions (lib/list_sort.c tools/ copy) Arnaldo Carvalho de Melo
2024-10-02 18:18 ` Namhyung Kim
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=Zv2A/npbGyP2SlKV@visitorckw-System-Product-Name \
--to=visitorckw@gmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.