From: Naman Jain <namjain@linux.microsoft.com>
To: gregkh@linuxfoundation.org, longli@microsoft.com,
ssengar@linux.microsoft.com, wei.liu@kernel.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tools/hv: fcopy: Fix irregularities with size of ring buffer" failed to apply to 6.6-stable tree
Date: Tue, 29 Jul 2025 14:45:34 +0530 [thread overview]
Message-ID: <676182d6-78cb-44a5-af99-e1e938ba6e9d@linux.microsoft.com> (raw)
In-Reply-To: <2025072131-stage-bundle-b616@gregkh>
On 7/21/2025 2:57 PM, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 6.6-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.6.y
> git checkout FETCH_HEAD
> git cherry-pick -x a4131a50d072b369bfed0b41e741c41fd8048641
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2025072131-stage-bundle-b616@gregkh' --subject-prefix 'PATCH 6.6.y' HEAD^..
>
> Possible dependencies:
>
>
>
> thanks,
>
> greg k-h
For 6.6 and older stable kernels, fcopy was not supported via
uio_hv_generic, so the "Fixes" change is not going to break fcopy
there. So, there is no need to port this change on these kernel
versions.
Regards,
Naman
prev parent reply other threads:[~2025-07-29 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:27 FAILED: patch "[PATCH] tools/hv: fcopy: Fix irregularities with size of ring buffer" failed to apply to 6.6-stable tree gregkh
2025-07-29 9:15 ` Naman Jain [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=676182d6-78cb-44a5-af99-e1e938ba6e9d@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=longli@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=stable@vger.kernel.org \
--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