From: Thomas Hellstrom <thomas@shipmail.org>
To: Thomas Hellstrom <thellstrom@vmware.com>,
Woody Suwalski <terraluna977@gmail.com>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
David Airlie <airlied@linux.ie>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
Deepak Singh Rawat <drawat@vmware.com>
Subject: Re: drm: fix vmwgfx boot warning WAS Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps
Date: Wed, 17 Jan 2018 09:19:48 +0100 [thread overview]
Message-ID: <23443229-05f4-a32f-59e0-d4c6b1d53231@shipmail.org> (raw)
In-Reply-To: <99d00cb3-2fb7-e238-12d6-386617fc5e03@vmware.com>
On 01/17/2018 07:33 AM, Thomas Hellstrom wrote:
> Hi, Woody,
>
> On 01/16/2018 10:39 PM, Woody Suwalski wrote:
>> Thomas, the same way my DRM patch has disappeared:
>> Date
>>
>> Tue, 19 Dec 2017 11:50:57 -0800
>> From Sinclair Yeh <>
>> Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
>>
>>
>>
>>
>> This looks okay to me.
>
> Since this is a core DRM patch I think Sinclair was expecting it to be
> pulled in using the drm-misc tree. Did you get a comment from Daniel
> on this patch?
>
> Thanks,
> Thomas
>
Actually, checkpatch.pl complains about -ENOSYS, so I'm sending a pull
request for v1 of this patch instead, to make everybody happy. I've
rephrased the commit log somewhat. Hope that's OK.
/Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Hellstrom <thomas@shipmail.org>
To: Thomas Hellstrom <thellstrom@vmware.com>,
Woody Suwalski <terraluna977@gmail.com>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
David Airlie <airlied@linux.ie>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
Deepak Singh Rawat <drawat@vmware.com>
Subject: Re: drm: fix vmwgfx boot warning WAS Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps
Date: Wed, 17 Jan 2018 09:19:48 +0100 [thread overview]
Message-ID: <23443229-05f4-a32f-59e0-d4c6b1d53231@shipmail.org> (raw)
In-Reply-To: <99d00cb3-2fb7-e238-12d6-386617fc5e03@vmware.com>
On 01/17/2018 07:33 AM, Thomas Hellstrom wrote:
> Hi, Woody,
>
> On 01/16/2018 10:39 PM, Woody Suwalski wrote:
>> Thomas, the same way my DRM patch has disappeared:
>> Date
>>
>> Tue, 19 Dec 2017 11:50:57 -0800
>> From Sinclair Yeh <>
>> Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
>>
>>
>>
>>
>> This looks okay to me.
>
> Since this is a core DRM patch I think Sinclair was expecting it to be
> pulled in using the drm-misc tree. Did you get a comment from Daniel
> on this patch?
>
> Thanks,
> Thomas
>
Actually, checkpatch.pl complains about -ENOSYS, so I'm sending a pull
request for v1 of this patch instead, to make everybody happy. I've
rephrased the commit log somewhat. Hope that's OK.
/Thomas
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
next prev parent reply other threads:[~2018-01-17 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 17:18 [PATCH] [RESEND] vmwgfx: use monotonic event timestamps Arnd Bergmann
2018-01-16 17:18 ` Arnd Bergmann
2018-01-16 17:28 ` Thomas Hellstrom
2018-01-16 17:28 ` Thomas Hellstrom
2018-01-16 21:39 ` Woody Suwalski
2018-01-16 21:39 ` Woody Suwalski
2018-01-17 6:33 ` drm: fix vmwgfx boot warning WAS " Thomas Hellstrom
2018-01-17 6:33 ` Thomas Hellstrom
2018-01-17 8:19 ` Thomas Hellstrom [this message]
2018-01-17 8:19 ` Thomas Hellstrom
2018-01-16 21:53 ` Arnd Bergmann
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=23443229-05f4-a32f-59e0-d4c6b1d53231@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=drawat@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terraluna977@gmail.com \
--cc=thellstrom@vmware.com \
--cc=y2038@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.