From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: patches@lists.linux.dev, stable <stable@kernel.org>
Subject: stable-queue.git: queue-6.15/series corrupted (duplicate temporary patches)
Date: Thu, 19 Jun 2025 02:50:21 +0200 [thread overview]
Message-ID: <20250619025021.0ee12258@mir> (raw)
Hi
While trying to bisect a potential issue in v6.15.3-rc1, I noticed that
queue-6.15/series of the current (v6.15.2-74-g344d39fc8d)
git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
seems to contain artifacts of duplicate patch entries:
upstream/drm-msm-dpu-remove-dsc-feature-bit-for-pingpong-on-m.patch-13942
upstream/drm-msm-dpu-remove-dsc-feature-bit-for-pingpong-on-m.patch-8756
upstream/arm64-dts-rockchip-disable-unrouted-usb-controllers-.patch-25959
Thank you for keeping both the traditional patch-6.15.3-rc1.gz and the
split out/ individual patches so easily testable, it really helps
(especially for bisecting).
Regards
Stefan Lippers-Hollmann
next reply other threads:[~2025-06-19 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 0:50 Stefan Lippers-Hollmann [this message]
2025-06-20 15:47 ` stable-queue.git: queue-6.15/series corrupted (duplicate temporary patches) Greg Kroah-Hartman
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=20250619025021.0ee12258@mir \
--to=s.l-h@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=patches@lists.linux.dev \
--cc=stable@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 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.