From: Sasha Levin <sashal@kernel.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Michael Kelley <mikelley@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, decui@microsoft.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.19 01/16] Drivers: hv: Never allocate anything besides framebuffer from framebuffer memory region
Date: Sat, 24 Sep 2022 23:18:31 -0400 [thread overview]
Message-ID: <Yy/IhxtFBvq0VoKN@sashalap> (raw)
In-Reply-To: <87illgog69.fsf@redhat.com>
On Wed, Sep 21, 2022 at 06:17:34PM +0200, Vitaly Kuznetsov wrote:
>Sasha Levin <sashal@kernel.org> writes:
>
>> From: Vitaly Kuznetsov <vkuznets@redhat.com>
>>
>> [ Upstream commit f0880e2cb7e1f8039a048fdd01ce45ab77247221 ]
>>
>
>(this comment applies to all stable branches)
>
>While this change seems to be worthy on its own, the underlying issue
>with Gen1 Hyper-V VMs won't be resolved without
>
>commit 2a8a8afba0c3053d0ea8686182f6b2104293037e
>Author: Vitaly Kuznetsov <vkuznets@redhat.com>
>Date: Sat Aug 27 15:03:44 2022 +0200
>
> Drivers: hv: Always reserve framebuffer region for Gen1 VMs
>
>as 'fb_mmio' is still going to be unset in some cases without it.
Which seems to fail building. Backports welcome :)
--
Thanks,
Sasha
prev parent reply other threads:[~2022-09-25 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:53 [PATCH AUTOSEL 5.19 01/16] Drivers: hv: Never allocate anything besides framebuffer from framebuffer memory region Sasha Levin
2022-09-21 16:17 ` Vitaly Kuznetsov
2022-09-25 3:18 ` Sasha Levin [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=Yy/IhxtFBvq0VoKN@sashalap \
--to=sashal@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).