From: Deepak Rawat <drawat.floss@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Dexuan Cui <decui@microsoft.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Cc: Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH v5 1/3] drm/hyperv: Add DRM driver for hyperv synthetic video device
Date: Thu, 27 May 2021 03:29:13 -0700 [thread overview]
Message-ID: <0e449c3d589d8999ea5ee392f2b72b437f65a604.camel@gmail.com> (raw)
In-Reply-To: <b093d480-c3f1-f2f7-1107-60195c0bea0c@suse.de>
On Wed, 2021-05-26 at 21:42 +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 20.05.21 um 07:41 schrieb Dexuan Cui:
> > > From: Deepak Rawat <drawat.floss@gmail.com>
> > > Sent: Wednesday, May 19, 2021 9:38 AM
> > > ...
> > > +static int hyperv_vmbus_suspend(struct hv_device *hdev)
> > > +{
> > > + struct drm_device *dev = hv_get_drvdata(hdev);
> > > + int ret;
> > > +
> > > + ret = drm_mode_config_helper_suspend(dev);
> >
> > If 'ret' is not zero, return immediately?
> >
> > > +
> > > + vmbus_close(hdev->channel);
> > > +
> > > + return ret;
> > > +}
> >
> >
> > > +MODULE_DESCRIPTION("DRM driver for hyperv synthetic video
> > > device");
> >
> > s/hyperv/Hyper-V ?
> >
>
> Maybe let's fix these points and then get the driver merged.
Hi Thomas, sure. This was on my list to fix before merge. One patch is
missing ack/review, so it would be nice if that also is reviewed.
Thanks,
Deepak
>
> Best regards
> Thomas
>
prev parent reply other threads:[~2021-05-27 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 16:37 [PATCH v5 1/3] drm/hyperv: Add DRM driver for hyperv synthetic video device Deepak Rawat
2021-05-19 16:37 ` [PATCH v5 2/3] drm/hyperv: Handle feature change message from device Deepak Rawat
2021-05-19 16:37 ` [PATCH v5 3/3] MAINTAINERS: Add maintainer for hyperv video device Deepak Rawat
2021-05-20 5:41 ` [PATCH v5 1/3] drm/hyperv: Add DRM driver for hyperv synthetic " Dexuan Cui
2021-05-26 19:42 ` Thomas Zimmermann
2021-05-27 10:29 ` Deepak Rawat [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=0e449c3d589d8999ea5ee392f2b72b437f65a604.camel@gmail.com \
--to=drawat.floss@gmail.com \
--cc=decui@microsoft.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=tzimmermann@suse.de \
/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).