Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: gregkh@linuxfoundation.org
Cc: aliceryhl@google.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] rust_binderfs: add transaction_report feature entry" failed to apply to 7.3-stable tree
Date: Wed, 4 Nov 2026 19:23:38 +0000	[thread overview]
Message-ID: <auuGOvKNKpJ1saa0@google.com> (raw)
In-Reply-To: <2026110401-lure-unmoving-2038@gregkh>

On Wed, Nov 04, 2026 at 03:12:01PM +0100, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 7.3-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> To reproduce the conflict and resubmit, you may use the following commands:
> 
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-7.3.y
> git checkout FETCH_HEAD
> git cherry-pick -x 2fcc8b9687af998b74ce6b0d349167eae7931558
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026110401-lure-unmoving-2038@gregkh' --subject-prefix 'PATCH 7.3.y' 'HEAD^..'
> 
> Possible dependencies:
> 
> 
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> From 2fcc8b9687af998b74ce6b0d349167eae7931558 Mon Sep 17 00:00:00 2001
> From: Carlos Llamas <cmllamas@google.com>
> Date: Wed, 16 Sep 2026 12:08:32 +0000
> Subject: [PATCH] rust_binderfs: add transaction_report feature entry
> 
> rust_binderfs is missing the equivalent of commit f37b55ded8ed ("binder:
> add transaction_report feature entry"), which adds "transaction_report"
> to the binderfs feature list. This helps userspace determine if the
> BINDER_CMD_REPORT from the generic netlink API is supported.
> 
> Cc: stable@vger.kernel.org
> Fixes: f14e0c8183bc ("rust_binder: report netlink transactions")
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> Link: https://patch.msgid.link/20260916120833.593407-1-cmllamas@google.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

This might have been my fault because I added the Cc: stable tag.
However, no backport is needed. The patch is already applied to the 7.3
tree as commit 137d6ccf0ec8 ("rust_binderfs: add transaction_report
feature entry").

--
Carlos Llamas

      reply	other threads:[~2026-11-04 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 14:12 FAILED: patch "[PATCH] rust_binderfs: add transaction_report feature entry" failed to apply to 7.3-stable tree gregkh
2026-11-04 19:23 ` Carlos Llamas [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=auuGOvKNKpJ1saa0@google.com \
    --to=cmllamas@google.com \
    --cc=aliceryhl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.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