From: Sean Hudson <sean_hudson@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Valentin Popa <valentin.popa@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] [V3]mesa: upgrade to 10.1.3
Date: Tue, 27 May 2014 11:16:54 -0500 [thread overview]
Message-ID: <5384BA76.4080700@mentor.com> (raw)
In-Reply-To: <CAJTo0Lb6Wa8tdyjB7yPK7w_PLuaKq9OKZAU8W+cXds+nt4PbeA@mail.gmail.com>
On 05/22/2014 11:58 AM, Burton, Ross wrote:
> For these three patches:
>
> On 22 May 2014 17:28, Valentin Popa <valentin.popa@intel.com> wrote:
>>> dri3proto: add it to oe-core
>>> libxshmfence: add it to oe-core
>>> eglinfo: patched to compile with mesa10+
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
>
> Mesa needs more testing, but these pieces are good to merge.
>
> Ross
>
I don't have a specific need to preserve MESA 9.x (that I know of
right now), but it seems like we might consider keeping it around a bit
longer in parallel with MESA 10.x and then formally deprecate it in the
next release.
Regards,
Sean
prev parent reply other threads:[~2014-05-27 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 16:49 [PATCH 0/4] [PATCH_V2]mesa: upgrade to 10.1.3 Valentin Popa
2014-05-21 16:49 ` [PATCH 1/4] dri3proto: add it to oe-core Valentin Popa
2014-05-21 16:50 ` [PATCH 2/4] libxshmfence: " Valentin Popa
2014-05-21 16:50 ` [PATCH 3/4] mesa: upgrade to 10.1.3 Valentin Popa
2014-05-21 18:33 ` Martin Jansa
2014-05-22 12:26 ` Valentin Popa
2014-05-22 13:23 ` Martin Jansa
2014-05-22 13:29 ` Valentin Popa
2014-05-21 16:50 ` [PATCH 4/4] eglinfo: patched to compile with mesa10+ Valentin Popa
2014-05-21 20:22 ` Burton, Ross
2014-05-22 12:28 ` Valentin Popa
2014-05-22 16:28 ` [PATCH 0/4] [V3]mesa: upgrade to 10.1.3 Valentin Popa
2014-05-22 16:58 ` Burton, Ross
2014-05-27 16:16 ` Sean Hudson [this message]
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=5384BA76.4080700@mentor.com \
--to=sean_hudson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=valentin.popa@intel.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 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.