Linux-Next discussions
 help / color / mirror / Atom feed
From: Arnaldo Melo <arnaldo.melo@gmail.com>
To: Mark Brown <broonie@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the perf tree
Date: Tue, 30 Jun 2026 07:23:20 -0300	[thread overview]
Message-ID: <A5DDF2CD-1DF0-43BE-8FA2-E2FABE176B27@gmail.com> (raw)
In-Reply-To: <akOX2cfUOK1rRbu0@sirena.org.uk>



On June 30, 2026 7:18:01 AM GMT-03:00, Mark Brown <broonie@kernel.org> wrote:
>Commits
>
>  535c327f22a28 ("perf python: Add LiveSession helper")
>  4f093d248b148 ("perf python: Add perf.pyi stubs file")
>  145f6bea48134 ("perf python: Add type checking for parse_events/parse_metrics")
>  1bb0a1721f3f1 ("perf python: Handle Py_None for thread and cpu maps")
>  226e60c35ac93 ("perf python: Add config file access")
>  2b8aad745c248 ("perf python: Add syscall name/id to convert syscall number and name")
>  6efb7ef71b226 ("perf python: Expose brstack in sample event")
>  1b3460930fcda ("perf python: Extend API for stat events in python.c")
>  4d97f00572c6f ("perf python: Add callchain support")
>  0dd3f949cfb58 ("perf python: Add mmap2 event")
>  b81c05a559ee7 ("perf python: Refactor and add accessors to sample event")
>  beed2f88c2d7b ("perf python: Add python session abstraction wrapping perf's session")
>  f46938e02fa6c ("perf python: Add wrapper for perf_data file abstraction")
>  d8da1ea834a88 ("perf python: Use evsel in sample in pyrf_event")
>  3e153b92b6e88 ("perf evlist: Add reference count checking")
>  4d7018b55734f ("perf evsel: Add reference count")
>  7e7110bdf0e37 ("perf evlist: Add reference count")
>  ca42447bde058 ("perf data: Add open flag")
>  3d295e4e6974a ("perf evsel/evlist: Avoid unnecessary #includes")
>  6a7ac633a3e8c ("perf python: Add missed explicit dependencies")
>  bdd53407c817d ("perf util: Sort includes and add missed explicit dependencies")
>
>are missing a Signed-off-by from their committers.

Thanks for reporting, I'll fix and force push,

- Arnaldo

  reply	other threads:[~2026-06-30 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 10:18 Missing signoff in the perf tree Mark Brown
2026-06-30 10:23 ` Arnaldo Melo [this message]
2026-06-30 11:43 ` Arnaldo Carvalho de Melo
2026-06-30 11:44   ` Mark Brown
2026-06-30 17:14     ` Namhyung Kim

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=A5DDF2CD-1DF0-43BE-8FA2-E2FABE176B27@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=namhyung@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