[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fX+kdRujgNAq8SVkkNwgnB383r38+AEmvon1k01R4X=kg@mail.gmail.com>
Date: Fri, 30 Jun 2023 10:06:20 -0700
From: Ian Rogers <irogers@...gle.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: linux-perf-users@...r.kernel.org, bpf@...r.kernel.org,
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>,
Ingo Molnar <mingo@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
Kan Liang <kan.liang@...ux.intel.com>,
Mark Rutland <mark.rutland@....com>,
Namhyung Kim <namhyung@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 13/13] perf parse-events: Remove ABORT_ON
On Fri, Jun 30, 2023 at 9:56 AM Markus Elfring <Markus.Elfring@....de> wrote:
>
> > Prefer informative messages rather than none with ABORT_ON. Document
> > one failure mode and add an error message for another.
>
> Does such a wording really fit to the known requirement “Solve only one problem per patch.”?
>
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4#n81
Sorry your explanation isn't clear. Please can you elaborate.
Thanks,
Ian
>
> Regards,
> Markus
Powered by blists - more mailing lists