From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/9] mesa: upgrade to 7.10.2
Date: Fri, 15 Apr 2011 12:40:02 -0700 [thread overview]
Message-ID: <4DA89F12.7040205@mentor.com> (raw)
In-Reply-To: <38033f4ff7f7cd735acf7d2e11ba078f4c2aafb6.1302846043.git.ke.yu@intel.com>
On 04/14/2011 10:44 PM, Yu Ke wrote:
> From: Yu Ke <ke.yu@intel.com>
>
> - also remove the talloc-removal.patch because it is already
> included in this version
> @@ -15,6 +14,6 @@ LIB_DEPS = "virtual/libx11 libxext libxxf86vm libxdamage libxfixes libxml2-nativ
> DEPENDS = "${PROTO_DEPS} ${LIB_DEPS} makedepend-native"
While we're in here, the mesa stuff needs python-native as a DEPENDS.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-04-15 19:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 5:44 [PATCH 0/9] recipes upgrade V2 Yu Ke
2011-04-15 5:44 ` [PATCH 1/9] libdrm: upgrade from 2.4.23 to 2.4.25 Yu Ke
2011-04-15 5:44 ` [PATCH 2/9] xf86-input-synaptics: upgrade from 1.3.0 to 1.4.0 Yu Ke
2011-04-15 5:44 ` [PATCH 3/9] xf86-input-vmmouse: upgrade from 12.6.10 to 12.7.0 Yu Ke
2011-04-15 5:44 ` [PATCH 4/9] mesa: upgrade to 7.10.2 Yu Ke
2011-04-15 16:42 ` Saul Wold
2011-04-16 4:38 ` Yu Ke
2011-04-16 5:06 ` Saul Wold
2011-04-15 19:40 ` Tom Rini [this message]
2011-04-16 4:39 ` Yu Ke
2011-04-15 5:44 ` [PATCH 5/9] evieext: upgrade from 1.1.0 to 1.1.1 Yu Ke
2011-04-15 5:44 ` [PATCH 6/9] xf86-input-mouse: upgrade from 1.6 to 1.7 Yu Ke
2011-04-15 5:44 ` [PATCH 7/9] pango: upgrade from 1.28.3 to 1.28.4 Yu Ke
2011-04-15 5:44 ` [PATCH 8/9] xf86-input-keyboard: upgrade from 1.5.0 to 1.6.0 Yu Ke
2011-04-15 5:44 ` [PATCH 9/9] xkbcomp: upgrade from 1.2.0 to 1.2.1 Yu Ke
2011-04-18 21:15 ` [PATCH 0/9] recipes upgrade V2 Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-04-11 1:28 [PATCH 0/9] upgrade recipes Yu Ke
2011-04-11 1:28 ` [PATCH 4/9] mesa: upgrade to 7.10.2 Yu Ke
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=4DA89F12.7040205@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@lists.openembedded.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