From: Namhyung Kim <namhyung@kernel.org>
To: Ricky Ringler <ricky.ringler@proton.me>
Cc: irogers@google.com, mingo@redhat.com, acme@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v6] perf utilities: cln_size header
Date: Mon, 6 Apr 2026 10:51:53 -0700 [thread overview]
Message-ID: <adPyuaptzUlTdpi6@google.com> (raw)
In-Reply-To: <adND6AGUKu8d0YlO@google.com>
On Sun, Apr 05, 2026 at 10:26:00PM -0700, Namhyung Kim wrote:
> On Sat, Apr 04, 2026 at 01:16:56AM +0000, Ricky Ringler wrote:
> > Forgive me for wasting your time with my last message...
> > I switched work machines and attached the wrong patch file.
>
> That's fine but you could send it as v7 so that the tools can pick the
> latest version without confusion.
>
> >
> > ---
>
> Also, adding this mark invalidates the following paragraphs and leave
> them out from the commit message.. I'll update it this time but keep
> that in mind for the next time.
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2026-04-06 17:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 4:07 [PATCH] perf utilities: cln_size header Ricky Ringler
2026-03-04 1:25 ` Namhyung Kim
2026-03-05 23:57 ` [PATCH v2] " Ricky Ringler
2026-03-06 0:12 ` Ricky Ringler
2026-03-08 17:20 ` [PATCH v3] " Ricky Ringler
2026-03-09 15:28 ` Ian Rogers
2026-03-21 20:41 ` [PATCH v4] " Ricky Ringler
2026-03-26 22:43 ` Namhyung Kim
2026-03-28 20:04 ` [PATCH v5] " Ricky Ringler
2026-03-30 7:16 ` kernel test robot
2026-03-31 6:37 ` Namhyung Kim
2026-04-03 22:08 ` [PATCH v6] " Ricky Ringler
2026-04-04 0:29 ` Namhyung Kim
2026-04-04 1:16 ` Ricky Ringler
2026-04-06 5:26 ` Namhyung Kim
2026-04-06 17:51 ` Namhyung Kim [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=adPyuaptzUlTdpi6@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ricky.ringler@proton.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.