All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Costa Shulyupin <costa.shul@redhat.com>,
	Crystal Wood <crwood@redhat.com>,
	Tomas Glozar <tglozar@redhat.com>
Subject: Re: [GIT PULL] tracing tools: RTLA updates for 7.2
Date: Tue, 16 Jun 2026 17:15:47 -0400	[thread overview]
Message-ID: <20260616171547.52d4c525@fedora> (raw)
In-Reply-To: <CAHk-=wjeUu+o_=zi_9zdPBfzXAxE_BVZM6bUV1Ky9JCgHmQ_0Q@mail.gmail.com>

On Tue, 16 Jun 2026 18:05:03 +0530
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Tue, 16 Jun 2026 at 01:55, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > - Migrate command line interface to libsubcmd  
> 
> I'm assuming the annoying conflicts - that you didn't mention - with
> commit e9e41d303503 ("rtla: Fix parsing of multi-character short
> options") are just "take the new code".
> 
> Becasue that's what I did. While swearing over the pointlessness of this all.

Sorry about that :-(  Unfortunately you opened the merge window while
I'm starting my new job, and I'm currently in London doing the
orientation all day for the the next two weeks. I only have a couple
hours a day to do upstream work while I'm here. I usually merge the
code into your branch to check for conflicts before sending them but I
don't usually do that for the tooling branch.

This conflict was reported by linux-next, but I simply forgot about it. :-(

-- Steve


  reply	other threads:[~2026-06-16 21:15 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
2026-06-16 12:35 ` Linus Torvalds
2026-06-16 21:15   ` Steven Rostedt [this message]
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=20260616171547.52d4c525@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 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.