Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] batman-adv: tp_meter: fix tp_num leak on kmalloc failure" failed to apply to 6.1-stable tree
Date: Fri, 15 May 2026 11:10:30 +0200	[thread overview]
Message-ID: <3081197.VdNmn5OnKV@sven-l14> (raw)
In-Reply-To: <2026051520-obnoxious-editor-0139@gregkh>

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

On Friday, 15 May 2026 10:45:20 CEST gregkh@linuxfoundation.org wrote:
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026051520-obnoxious-editor-0139@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..

@Greg, I will take care of backporting the failed batman-adv patches in an 
hour or so. The steps you provide in the mail are always super helpful to stay 
focused and do everything step by step. 

But I've noticed that on a shell with "extended_glob" enabled, the shell tries 
to match the last parameter because it sees the '^' character. Maybe you could 
also quote it too:

-git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026051520-obnoxious-editor-0139@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
+git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026051520-obnoxious-editor-0139@gregkh' --subject-prefix 'PATCH 6.1.y' 'HEAD^..'

Btw. I've just disabled it here on my shell. But maybe this is still 
interesting for others

Thanks,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-15  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  8:45 FAILED: patch "[PATCH] batman-adv: tp_meter: fix tp_num leak on kmalloc failure" failed to apply to 6.1-stable tree gregkh
2026-05-15  9:10 ` Sven Eckelmann [this message]
2026-05-15 11:52 ` [PATCH 6.1.y] batman-adv: tp_meter: fix tp_num leak on kmalloc failure Sven Eckelmann

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=3081197.VdNmn5OnKV@sven-l14 \
    --to=sven@narfation.org \
    --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