From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: John Garry <john.garry@huawei.com>,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, irogers@google.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Stop depending on .git files for building PERF-VERSION-FILE
Date: Wed, 30 Mar 2022 11:30:09 -0300 [thread overview]
Message-ID: <YkRpcW4PkVH59axm@kernel.org> (raw)
In-Reply-To: <YkRo/PtIf9aOqpZV@kernel.org>
Em Wed, Mar 30, 2022 at 11:28:12AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Mar 30, 2022 at 04:22:35PM +0200, Matthieu Baerts escreveu:
> > On 30/03/2022 16:12, Arnaldo Carvalho de Melo wrote:
> > >> Thank you for your patch, I just tested it and it also fixes the issue I
> > >> reported!
> > > I'm taking this as a:
> > > Tested-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> > > Ok?
> > Yes, OK for me, thank you!
> > I never know what maintainers prefer when there is already a
> > "Reported-by" tag so I didn't specify it but I will do next time.
> Right, I'll stick both R-by and T-by.
> There are cases where people just report and don't test, or just ack.
But when you actually provide the:
Tested-by: Matthieu Baerts <matthieu.baerts@tessares.net>
It makes the lives of maintainers using b4 easier, as it'll collect
those.
About b4: https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
- Arnaldo
next prev parent reply other threads:[~2022-03-30 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:22 [PATCH] perf tools: Stop depending on .git files for building PERF-VERSION-FILE John Garry
2022-03-30 13:22 ` Matthieu Baerts
2022-03-30 14:12 ` Arnaldo Carvalho de Melo
2022-03-30 14:22 ` Matthieu Baerts
2022-03-30 14:28 ` Arnaldo Carvalho de Melo
2022-03-30 14:30 ` Arnaldo Carvalho de Melo [this message]
2022-03-30 14:36 ` Matthieu Baerts
2022-03-30 16:30 ` Arnaldo Carvalho de Melo
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=YkRpcW4PkVH59axm@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthieu.baerts@tessares.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).