All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	helpdesk@kernel.org, Konstantin  Ryabitsev <mricon@kernel.org>
Subject: Re: Documentation update to KernelShark
Date: Tue, 9 Jun 2026 11:22:23 -0400	[thread overview]
Message-ID: <20260609112223.3a17b5ba@fedora> (raw)
In-Reply-To: <914607e6-1a51-e872-6383-292efecec61e@gmail.com>

On Thu, 4 Jun 2026 12:57:48 +0300
Yordan Karadzhov <y.karadz@gmail.com> wrote:

> Hi Steven,
> 
> I am very happy to see a patch from you :-)
> 
> The patch has been applied to the repo.
> 
> I do have a PatchWork account. My username is ykaradzhov.

Hi Konstantin,

Is it possible to add Yordan's id to the list of possible "delegate to"
entries? This is for "Linux-Trace Development":

  https://patchwork.kernel.org/project/linux-trace-devel/list/

Thanks,

-- Steve


> 
> Cheers,
> Yordan
> 
> 
> On 5/29/26 18:55, Steven Rostedt wrote:
> > Hi Yordan,
> > 
> > Can you apply this patch to the  repo:
> > 
> >    https://patchwork.kernel.org/project/linux-trace-devel/patch/20251031115513.41b86970@gandalf.local.home/
> > 
> > Also, you probably should have your name added to the PatchWork so that
> > I can delegate KernelShark patches to you, and that will make it easier
> > for what is needed for KernelShark.
> > 
> > Do you have PatchWork account? If not, we should get you one (I Cc'd
> > helpdesk@kernel.org to let them know you need one too).
> > 
> > -- Steve  


  reply	other threads:[~2026-06-09 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 15:55 Documentation update to KernelShark Steven Rostedt
2026-06-04  9:57 ` Yordan Karadzhov
2026-06-09 15:22   ` Steven Rostedt [this message]
2026-06-10  4:25     ` Christopher Hoy Poy

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=20260609112223.3a17b5ba@fedora \
    --to=rostedt@goodmis.org \
    --cc=helpdesk@kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mricon@kernel.org \
    --cc=y.karadz@gmail.com \
    /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.