From: Wei Liu <wei.liu@kernel.org>
To: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
Cc: Dexuan Cui <decui@microsoft.com>,
Saurabh Singh Sengar <ssengar@microsoft.com>,
"drawat.floss@gmail.com" <drawat.floss@gmail.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
Wei Liu <wei.liu@kernel.org>
Subject: Re: [PATCH v4] drm/hyperv: Add error message for fb size greater than allocated
Date: Tue, 3 May 2022 15:08:06 +0000 [thread overview]
Message-ID: <20220503150806.neeemkwlexmyqsnd@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20220503145016.GA25079@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Tue, May 03, 2022 at 07:50:16AM -0700, Saurabh Singh Sengar wrote:
> On Tue, Apr 12, 2022 at 05:06:07AM +0000, Dexuan Cui wrote:
> > > From: Saurabh Sengar <ssengar@linux.microsoft.com>
> > > Sent: Monday, April 11, 2022 9:29 PM
> > > ...
> > > Add error message when the size of requested framebuffer is more than
> > > the allocated size by vmbus mmio region for framebuffer
> >
> > The line lacks a period, but I guess the maintainer may help fix it for you :-)
> >
> > > Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> >
> > Reviewed-by: Dexuan Cui <decui@microsoft.com>
>
> Can this be queued for next ? please let me know in case any clarification required.
Applied to hyperv-next. Thanks.
prev parent reply other threads:[~2022-05-03 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 4:28 [PATCH v4] drm/hyperv: Add error message for fb size greater than allocated Saurabh Sengar
2022-04-12 5:06 ` Dexuan Cui
2022-05-03 14:50 ` Saurabh Singh Sengar
2022-05-03 15:08 ` Wei Liu [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=20220503150806.neeemkwlexmyqsnd@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=decui@microsoft.com \
--cc=drawat.floss@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
/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