From: Steven Rostedt <rostedt@goodmis.org>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Costa Shulyupin <costa.shul@redhat.com>,
Crystal Wood <crwood@redhat.com>
Subject: Re: [GIT PULL] tracing tools: RTLA updates for 7.2
Date: Tue, 16 Jun 2026 17:22:16 -0400 [thread overview]
Message-ID: <20260616172216.1357f77b@fedora> (raw)
In-Reply-To: <CAP4=nvTL8iCtmADrDeyjE0+E-V-vBYdq9fgvbrTKJW6=d3beYw@mail.gmail.com>
On Tue, 16 Jun 2026 08:48:11 +0200
Tomas Glozar <tglozar@redhat.com> wrote:
> It appears that you missed my second pull request [1] with two fixes
> of issues that slipped through into the first one. Should I name it
> differently, or perhaps ping you about it earlier (e.g. if you don't
> pick it before the merge window) next time? (I did not do so, because
> I thought you just did not push tools/for-next yet and will do so when
> doing the 7.2 tag.)
>
> [1] https://lore.kernel.org/linux-trace-kernel/20260605140209.101548-1-tglozar@redhat.com/
Sorry, I completely missed this due to being on vacation and then
getting ready for my next trip.
Can you rebase on the commit that Linus pulled your commits in:
6b5a2b7d9bc156e505f09e698d85d6a1547c1206
So that it has the merge conflicts solved.
Thanks,
-- Steve
next prev parent reply other threads:[~2026-06-16 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 20:25 [GIT PULL] tracing tools: RTLA updates for 7.2 Steven Rostedt
2026-06-16 6:48 ` Tomas Glozar
2026-06-16 21:22 ` Steven Rostedt [this message]
2026-06-16 12:35 ` Linus Torvalds
2026-06-16 21:15 ` Steven Rostedt
2026-06-16 12:36 ` pr-tracker-bot
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=20260616172216.1357f77b@fedora \
--to=rostedt@goodmis.org \
--cc=costa.shul@redhat.com \
--cc=crwood@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglozar@redhat.com \
--cc=torvalds@linux-foundation.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