dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Greg Hackmann <ghackmann@google.com>
Cc: emil.l.velikov@gmail.com,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm] Add missing <strings.h> includes
Date: Thu, 23 Apr 2015 16:56:04 +0000	[thread overview]
Message-ID: <55392424.6000603@gmail.com> (raw)
In-Reply-To: <CAJKQeMaUYSPEj0XCujFd5ngZqwAXD2XXaxQ=JrEqPhDfF__zsg@mail.gmail.com>

On 22/04/15 16:19, Greg Hackmann wrote:
> On Tue, Apr 21, 2015 at 11:31 AM, Emil Velikov <emil.l.velikov@gmail.com> wrote:
>>
>> I'm not sure why I haven't hit this while building with Android-x86's
>> bionic, although it's the right thing to do.
> 
> Maybe a difference in bionic versions?  I know the bionic team made
> some recent (post-5.1) changes that unintentionally exposed a handful
> of other missing #includes in our tree.
> 
Could be. I've never really bothered checking the bionic (both
downstream patches and version) that Android-x86 uses.

>> From a quick look I cannot see libdrm in the AOSP build. Are you
>> experimenting with a libdrm based hwcompositor again :-)
> 
> Yeah.  That's where I want to end up in the long term, anyway.  I've
> said publicly that we'd eventually like to converge with upstream on
> this, and I still mean it.  :)
> 
Great glad to hear. We have a GSoC student that is working on it this
summer, so things might be closer than expected.

May I suggest that you ping/send patches to the list early and often.
There is a lot of traffic, and most people are busy with their own
hardware so patches do get missed/forgotten.

Another good idea is to pop over at #dri-devel at FreeNode, and have a
chat with the guys in real time - someone might be able to find a
solution/steer you in the right direction :-)

Cheers,
Emil

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-04-23 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 17:55 [PATCH libdrm] Add missing <strings.h> includes Greg Hackmann
2015-04-21 18:31 ` Emil Velikov
2015-04-22 16:19   ` Greg Hackmann
2015-04-23 16:56     ` Emil Velikov [this message]
2015-04-27  7:09       ` Chih-Wei Huang

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=55392424.6000603@gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ghackmann@google.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