[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAM9d7ciTZGuoT=D2i+uYG8mcNdFVnYi-Rvue5sbDZAyb24eRrA@mail.gmail.com>
Date: Fri, 23 Jun 2023 11:00:30 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: James Clark <james.clark@....com>,
linux-perf-users@...r.kernel.org, spoorts2@...ibm.com,
kernel-janitors@...r.kernel.org,
Adrian Hunter <adrian.hunter@...el.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Athira Rajeev <atrajeev@...ux.vnet.ibm.com>,
Ian Rogers <irogers@...gle.com>,
Ingo Molnar <mingo@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
Kajol Jain <kjain@...ux.ibm.com>,
Mark Rutland <mark.rutland@....com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>, cocci@...ia.fr
Subject: Re: [PATCH] perf tests: Fix test_arm_callgraph_fp variable expansion
On Fri, Jun 23, 2023 at 9:56 AM Markus Elfring <Markus.Elfring@....de> wrote:
>
> …
> > At the same time silence the shellcheck warning for that line and fix
> > two more shellcheck errors at the end of the script.
>
> Does such a wording really fit to the known requirement “Solve only one problem per patch.”?
Maybe not, but I think it still falls into the shellcheck category.
I don't mind having those trivial fixes together.
Applied to perf-tools-next, thanks!
>
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4-rc7#n81
Powered by blists - more mailing lists