From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ian Rogers <irogers@google.com>
Cc: Sasha Levin <sashal@kernel.org>,
Markus Elfring <Markus.Elfring@web.de>,
linux-perf-users@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Ivan Babrou <ivan@cloudflare.com>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [PATCH v2] perf unwind: Fix map reference counts
Date: Tue, 27 Jun 2023 08:32:36 +0300 [thread overview]
Message-ID: <a9732501-3eff-4b94-a9b2-53e5e5e5be1d@kadam.mountain> (raw)
In-Reply-To: <CAP-5=fWDnLDox3apMmvXmzVurFA=+sj7SEOOD7_2fam2VrGokA@mail.gmail.com>
Ah, great. Thanks, Ian.
The Reference Count Checking page is good information. There is a bunch
of interest in doing better QC so this stuff is good to know.
So in this case, it's probably difficult to assign a Fixes tag and that's
fine. Whatever. But I'm not a huge fan of the "Leave off the Fixes tag"
approach to preventing backports. There should be a better system for
that. Maybe there should be a tag for that? Or possibly that's too
complicated... I'm not sure.
Anyway, let's leave it for now. If it's really a problem then we'll run
into it again later and we can think about it at that point.
regards,
dan carpenter
prev parent reply other threads:[~2023-06-27 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 4:31 Ian Rogers
2023-06-23 5:01 ` Namhyung Kim
[not found] ` <64741e8e-e81a-afb9-9ce3-9c2d6baab44a@web.de>
2023-06-23 17:49 ` Ian Rogers
2023-06-23 17:58 ` Namhyung Kim
2023-06-26 12:42 ` Dan Carpenter
2023-06-26 17:38 ` Ian Rogers
2023-06-27 5:32 ` Dan Carpenter [this message]
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=a9732501-3eff-4b94-a9b2-53e5e5e5be1d@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=Markus.Elfring@web.de \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=cocci@inria.fr \
--cc=irogers@google.com \
--cc=ivan@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®