From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: mesa-dev@lists.freedesktop.org,
Kenneth Graunke <kenneth@whitecape.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 mesa] vk/intel: use negative VK_NO_PROTOTYPES scheme
Date: Mon, 9 May 2016 16:50:18 +0100 [thread overview]
Message-ID: <20160509155018.GL7910@imgtec.com> (raw)
In-Reply-To: <CAOFGe95=Xbz57jBGXQDt26d4n7s85SHa5KmDzNDA1aGKE3kuvQ@mail.gmail.com>
On Sun, May 01, 2016 at 09:39:58PM -0700, Jason Ekstrand wrote:
> On May 1, 2016 6:04 PM, "Kenneth Graunke" <kenneth@whitecape.org> wrote:
> > On Sunday, May 1, 2016 9:51:00 AM PDT Emil Velikov wrote:
> > > Adding the anv authors.
> > >
> > > Jason, Chad, is there a canonical place where changes to
> > > vulkan_intel.h should land first ? Eric has a nice fix which we want
> > > in mesa.
> > >
> > > Thanks
> > > Emil
> >
> > I'm pretty sure Mesa is the only repository where this lives.
>
> Yup
Ping?
I'm not sure why this didn't get at least an ACK from Intel, but I don't
see any reason not to apply this fix.
I don't have commit access; Emil, can you do it?
Cheers,
Eric
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
next prev parent reply other threads:[~2016-05-09 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461232428-17482-1-git-send-email-eric.engestrom@imgtec.com>
[not found] ` <1461234265-27828-1-git-send-email-eric.engestrom@imgtec.com>
[not found] ` <CACvgo50DC8MV9hQbo2rnZfmKe0WdwKNPwnBPoyEPKsrVAjJW8w@mail.gmail.com>
2016-04-28 18:13 ` [Mesa-dev] [PATCH v2 mesa] vk/intel: use negative VK_NO_PROTOTYPES scheme Eric Engestrom
2016-05-01 8:51 ` Emil Velikov
2016-05-02 1:04 ` Kenneth Graunke
2016-05-02 4:39 ` Jason Ekstrand
2016-05-09 15:50 ` Eric Engestrom [this message]
2016-05-09 22:13 ` [Mesa-dev] " Chad Versace
2016-05-09 23:13 ` Jason Ekstrand
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=20160509155018.GL7910@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.org \
--cc=mesa-dev@lists.freedesktop.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