All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: <gregkh@linuxfoundation.org>, <andy.liang@hpe.com>,
	<ardb@kernel.org>, <stefanb@linux.ibm.com>, <tiwai@suse.de>
Cc: <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] tpm: Change to kvalloc() in eventlog/acpi.c" failed to apply to 6.1-stable tree
Date: Mon, 10 Feb 2025 19:28:30 +0200	[thread overview]
Message-ID: <D7OXYNUO3XL2.2E2PL64Q9Z4KQ@kernel.org> (raw)
In-Reply-To: <2025021024-rover-consensus-cde2@gregkh>

On Mon Feb 10, 2025 at 5:00 PM EET, gregkh wrote:
>
> The patch below does not apply to the 6.1-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-6.1.y
> git checkout FETCH_HEAD
> git cherry-pick -x a3a860bc0fd6c07332e4911cf9a238d20de90173
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2025021024-rover-consensus-cde2@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..

Since this was with fresh HPE hardware and never seen otherwise,
do we want to backport? I don't see much utilitiritian value but
am open for other views too.

BR, Jarkko

      reply	other threads:[~2025-02-10 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 15:00 FAILED: patch "[PATCH] tpm: Change to kvalloc() in eventlog/acpi.c" failed to apply to 6.1-stable tree gregkh
2025-02-10 17:28 ` Jarkko Sakkinen [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=D7OXYNUO3XL2.2E2PL64Q9Z4KQ@kernel.org \
    --to=jarkko@kernel.org \
    --cc=andy.liang@hpe.com \
    --cc=ardb@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=stefanb@linux.ibm.com \
    --cc=tiwai@suse.de \
    /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.