From: Helge Deller <deller@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Wei Liu <wei.liu@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the fbdev tree
Date: Tue, 11 Mar 2025 07:22:00 +0100 [thread overview]
Message-ID: <efa8ffb6-2d6f-4007-94d9-2e41b4e7410a@gmx.de> (raw)
In-Reply-To: <20250311143021.0cc40c0e@canb.auug.org.au>
On 3/11/25 04:30, Stephen Rothwell wrote:
> The following commit is also in the hyperv-fixes tree as a different
> commit (but the same patch):
>
> f2b558988c7d ("fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs")
>
> This is comment
>
> 304386373007 ("fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs")
>
> in the hyperv-fixes tree.
I've dropped that patch from the fbdev tree.
Helge
next prev parent reply other threads:[~2025-03-11 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 3:30 Stephen Rothwell
2025-03-11 6:22 ` Helge Deller [this message]
2025-03-11 15:05 ` Wei Liu
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=efa8ffb6-2d6f-4007-94d9-2e41b4e7410a@gmx.de \
--to=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wei.liu@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
all inboxes | Powered by JetHome®