From: Pekka Paalanen <ppaalanen@gmail.com>
To: Hyungwon Hwang <human.hwang@samsung.com>
Cc: Emil Velikov <emil.l.velikov@gmail.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 3/6] xf86drmMode: Make atomic request structures visible
Date: Fri, 21 Aug 2015 09:44:42 +0300 [thread overview]
Message-ID: <20150821094442.7ebc6b39@gmail.com> (raw)
In-Reply-To: <20150821150658.50d3f2be@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 946 bytes --]
On Fri, 21 Aug 2015 15:06:58 +0900
Hyungwon Hwang <human.hwang@samsung.com> wrote:
> Hi Emil,
>
> On Thu, 20 Aug 2015 17:23:09 +0100
> Emil Velikov <emil.l.velikov@gmail.com> wrote:
>
> > On 19 August 2015 at 01:58, Hyungwon Hwang <human.hwang@samsung.com>
> > wrote:
> > > This patch makes 'struct _drmModeAtomicReqItem' and 'struct
> > > _drmModeAtomicReq' visible from outside. This is needed for
> > > userspace applications to use those structures when calling
> > > drmModeAtomicCommit().
Yeah, this sounds like a very bad idea.
Thanks,
pq
> > >
> > Hmmm what is missing in the current API, that one needs direct access
> > to the structs ? If we expose these to the user we'll be putting a
> > (ABI) hedgehog down our pants (i.e. it might be ok, but will likely
> > result in a very painful experience).
>
> I also agree with you. I think I should drop this patch, and find
> another way for modetest.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-08-21 6:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 0:58 [PATCH 1/6] xf86drmMode: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 2/6] xf86drmMode: separate drmModeAtomicCommit() and drmModeAtomicCleanup() Hyungwon Hwang
2015-08-20 16:17 ` Emil Velikov
2015-08-21 4:54 ` Hyungwon Hwang
2015-08-21 6:42 ` Pekka Paalanen
2015-08-21 7:18 ` Hyungwon Hwang
2015-08-21 10:08 ` Pekka Paalanen
2015-08-19 0:58 ` [PATCH 3/6] xf86drmMode: Make atomic request structures visible Hyungwon Hwang
2015-08-20 16:23 ` Emil Velikov
2015-08-21 6:06 ` Hyungwon Hwang
2015-08-21 6:44 ` Pekka Paalanen [this message]
2015-08-21 7:35 ` Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 4/6] modetest: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 5/6] modetest: add atomic modeset support Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 6/6] modetest: add atomic page flip support Hyungwon Hwang
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=20150821094442.7ebc6b39@gmail.com \
--to=ppaalanen@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=human.hwang@samsung.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