From: Martin Peres <martin.peres-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>,
Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>,
Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Cc: Manasi Navare
<manasi.d.navare-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [RFC PATCH xserver] modesetting: re-set the crtc's mode when link-status goes BAD
Date: Thu, 16 Feb 2017 09:56:16 +0200 [thread overview]
Message-ID: <a5afb22c-8de0-aa48-ecd7-c43478aa9774@linux.intel.com> (raw)
In-Reply-To: <87k28tkdiq.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
On 13/02/17 23:05, Eric Anholt wrote:
> I was just trying to provide review to get the kernel unstuck. The
> kernel should not be blocked until the patch gets lands (this obviously
> isn't the case with ioctls, which *don't* land in userspace until kernel
> does), you just need userspace published and generally agreed that the
> ABI works.
>
Yeah, I found it a bit odd too that we would get such requirement.
Anyway, thanks for taking the time, we will take this as an ACK from
your side, which should be enough to merge the patch in the kernel.
Thanks!
Martin
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
next prev parent reply other threads:[~2017-02-16 7:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 12:37 [RFC PATCH xserver] modesetting: re-set the crtc's mode when link-status goes BAD Martin Peres
2017-01-26 17:21 ` Daniel Vetter
[not found] ` <20170126172120.iflf5b5l4m4wsuus-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-01-31 17:08 ` Manasi Navare
2017-02-01 10:17 ` Jani Nikula
2017-01-31 20:13 ` Eric Anholt
2017-02-01 10:03 ` Jani Nikula
2017-02-01 19:58 ` Eric Anholt
2017-02-01 20:05 ` Manasi Navare
[not found] ` <20170201200512.GC21934-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-02-02 23:30 ` Martin Peres
[not found] ` <32b846ee-69c5-1dea-eed4-1bc41bb2958f-GANU6spQydw@public.gmane.org>
2017-02-03 0:30 ` Manasi Navare
2017-02-03 8:04 ` Daniel Vetter
[not found] ` <20170203080451.vrbmoaioqjyd3hhc-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-02-06 15:50 ` Martin Peres
[not found] ` <4f8317ff-53e8-4c2d-effa-d074b11b15e6-GANU6spQydw@public.gmane.org>
2017-02-08 16:37 ` Martin Peres
[not found] ` <069473c6-d75e-48eb-e75d-4e65e201b4fb-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-02-13 21:05 ` Eric Anholt
2017-02-13 23:14 ` Manasi Navare
[not found] ` <87k28tkdiq.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2017-02-16 7:56 ` Martin Peres [this message]
2017-02-24 20:09 ` Manasi Navare
2017-02-26 19:42 ` Daniel Vetter
2017-02-28 4:07 ` Navare, Manasi D
2017-02-28 8:42 ` Daniel Vetter
2017-02-02 9:01 ` Daniel Vetter
2017-02-02 17:57 ` Eric Anholt
2017-02-28 8:43 ` Daniel Vetter
2017-02-01 19:55 ` Manasi Navare
[not found] ` <20170126123728.5680-1-martin.peres-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-27 14:12 ` Martin Peres
2017-03-31 0:37 ` Eric Anholt
2017-03-31 0:50 ` Manasi Navare
2017-03-31 20:08 ` Eric Anholt
[not found] ` <87d1cxw6nq.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2017-03-31 20:17 ` Manasi Navare
2017-04-01 0:22 ` Eric Anholt
2017-04-02 12:28 ` Daniel Vetter
[not found] ` <20170402122809.trh7oxzz25oao4bu-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-04-03 2:21 ` Eric Anholt
[not found] ` <87efxamdt6.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2017-04-03 6:25 ` Manasi Navare
2017-04-03 7:19 ` Daniel Vetter
2017-04-05 18:13 ` Manasi Navare
2017-04-06 17:15 ` Manasi Navare
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=a5afb22c-8de0-aa48-ecd7-c43478aa9774@linux.intel.com \
--to=martin.peres-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=daniel-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org \
--cc=manasi.d.navare-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=martin.peres-GANU6spQydw@public.gmane.org \
--cc=xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.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).