[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cgXuSMbV2hMKZqUQOHU=c7Gix2sxh4C=BbLNSJEaZX6Yg@mail.gmail.com>
Date: Thu, 16 Jan 2025 11:08:23 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Chun-Tse Shao <ctshao@...gle.com>
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...hat.com,
acme@...nel.org, mark.rutland@....com, alexander.shishkin@...ux.intel.com,
jolsa@...nel.org, irogers@...gle.com, adrian.hunter@...el.com,
kan.liang@...ux.intel.com, nick.forrington@....com,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v5 3/3] perf lock: Rename fields in lock_type_table
Hello,
On Wed, Dec 11, 2024 at 11:20 AM Namhyung Kim <namhyung@...nel.org> wrote:
>
> On Tue, Dec 10, 2024 at 12:08:22PM -0800, Chun-Tse Shao wrote:
> > `lock_type_table` contains `name` and `str` which can be confusing.
> > Rename them to `flags_name` and `lock_name` and add descriptions to
> > enhance understanding.
> > Tested by building perf for x86.
> >
> > Signed-off-by: Chun-Tse Shao <ctshao@...gle.com>
>
> Reviewed-by: Namhyung Kim <namhyung@...nel.org>
I'm trying to process this patchset but it doesn't apply to perf-tools-next
anymore. Can you please rebase?
Thanks,
Namhyung
Powered by blists - more mailing lists