From: Sasha Levin <sashal@kernel.org>
To: Bradley Morgan <brads@mainlining.org>
Cc: stable@vger.kernel.org, Daehyeon Ko <4ncienth@gmail.com>,
syzbot+0aee5e8066eddbbe7397@syzkaller.appspotmail.com,
syzbot+e8b3520b53e78e90034e@syzkaller.appspotmail.com,
Oleg Nesterov <oleg@redhat.com>,
"Christian Brauner (Amutable)" <brauner@kernel.org>
Subject: Re: [PATCH 6.18.y 3/3] exit: hold a reference to thread_pid across proc_flush_pid
Date: Wed, 16 Sep 2026 16:56:49 -0400 [thread overview]
Message-ID: <aqsCkQKOgLUtjml1@laps> (raw)
In-Reply-To: <E01AAD86-816E-4B90-9D5D-E4281573ACBA@mainlining.org>
On Wed, Sep 16, 2026 at 09:47:29PM +0100, Bradley Morgan wrote:
>Do you manually do all these? Or use a AI program to do these.
Some LLM, and some other tools that don't involve LLMs.
>If you use a AI program to do automated backporting, please add something
>like:
>
>[LLM: Thing it's done to fix the conflict]
That gets added on commits that get modified by the LLM to backport cleanly. An
example would be:
https://lore.kernel.org/all/20260916204117.2702377-1-sashal@kernel.org/
In this instance, there were no LLM tools involved in the resolution of the
conflict. Instead, I took two prerequesite commits which allowed this last one
to apply cleanly, thus there is no backport note on it.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-16 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 15:16 FAILED: patch "[PATCH] exit: hold a reference to thread_pid across proc_flush_pid" failed to apply to 6.18-stable tree gregkh
2026-09-16 20:36 ` [PATCH 6.18.y 1/3] ns: add __ns_ref_read() Sasha Levin
2026-09-16 20:36 ` [PATCH 6.18.y 2/3] ns: rename to exit_nsproxy_namespaces() Sasha Levin
2026-09-16 20:36 ` [PATCH 6.18.y 3/3] exit: hold a reference to thread_pid across proc_flush_pid Sasha Levin
2026-09-16 20:47 ` Bradley Morgan
2026-09-16 20:56 ` Sasha Levin [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=aqsCkQKOgLUtjml1@laps \
--to=sashal@kernel.org \
--cc=4ncienth@gmail.com \
--cc=brads@mainlining.org \
--cc=brauner@kernel.org \
--cc=oleg@redhat.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+0aee5e8066eddbbe7397@syzkaller.appspotmail.com \
--cc=syzbot+e8b3520b53e78e90034e@syzkaller.appspotmail.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.