Live Patching
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <mpdesouza@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>, live-patching@vger.kernel.org
Cc: Jiri Kosina <jikos@kernel.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	 Miroslav Benes	 <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
	Song Liu <song@kernel.org>
Subject: Re: Sashiko patch review for live-patching?
Date: Wed, 13 May 2026 15:43:57 -0300	[thread overview]
Message-ID: <4f5c20003e064cea830ce1e1b135b66c33538714.camel@suse.com> (raw)
In-Reply-To: <agSjM8dxgnV9QQaf@redhat.com>

On Wed, 2026-05-13 at 12:13 -0400, Joe Lawrence wrote:
> Hello live-patching maintainers,
> 
> I've noticed several references to the Sashiko (https://sashiko.dev/)
> kernel review bot on this list and was wondering if there is interest
> in
> adding live-patching to the mailing lists Sashiko tracks.
> 
> Integration appears straightforward: we can submit an MR to add our
> entry to sashiko-k8s.yaml and customize the bot's email behavior in
> email_policy.toml.
> 
> Full Sashiko Maintainer documentation is available here:
> https://github.com/sashiko-dev/sashiko/blob/main/MAINTAINERS_GUIDE.md
> 
> Personally, I would vote to set reply_to_author.  I don't have a
> strong
> opinion on the other custom options, provided that the CC list is
> opt-in
> rather than simply mirrored from the MAINTAINERS::LIVE PATCHING file.
> Either way, I've found the Sashiko web interface very helpful in
> patch
> review.

We can start with reply_to_author for some time before opting for
reply_all. At least in my last patches, it was quite good and helpful.

> 
> --
> Joe
> 

  parent reply	other threads:[~2026-05-13 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 16:13 Sashiko patch review for live-patching? Joe Lawrence
2026-05-13 17:17 ` Song Liu
2026-05-13 19:47   ` Josh Poimboeuf
2026-05-14  6:52     ` Miroslav Benes
2026-05-14  7:21     ` Petr Mladek
2026-05-14 15:45       ` Song Liu
2026-05-13 18:43 ` Marcos Paulo de Souza [this message]
2026-05-14 16:59 ` Joe Lawrence

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=4f5c20003e064cea830ce1e1b135b66c33538714.camel@suse.com \
    --to=mpdesouza@suse.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.com \
    --cc=song@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