Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/3] powervr: add powervr virtual package
Date: Fri, 12 Jul 2013 18:19:07 +0200	[thread overview]
Message-ID: <20130712181907.1d514e82@skate> (raw)
In-Reply-To: <1373639678-7357-1-git-send-email-spenser@gillilanding.com>

Dear Spenser Gilliland,

On Fri, 12 Jul 2013 09:34:36 -0500, Spenser Gilliland wrote:
> 
> Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Sundareson, Prabindh <prabu@ti.com>
> Cc: Peter Korsgaard <jacmet@uclibc.org>
> Cc: Sinan Akpolat <sinan@linkas.com.tr>
> ---
> v5:
>  - Fixed build issues on hard float (and non-CS toolchains)
>  - added powervr virtual package
> v4:
>  - Fix header issue with qt.
>  - Add eglimage version installation.
> v3:
>  - integrate reviews from thomas.
>  - Add qt patch
> v2:
>  - Take into account reviews.
>  - Simplfy init script.
>  - Fix header installation.
> v1:
>  - Added .pc files
>  - all review issues addressed
> RFC v3:
>  - all reviews addressed
>  - added demos
>  - added hard float (not runtime tested)
>  - added init script
>  - added SGX detection script (untested)
>  - tested on beaglexm using demos
> RFC v2:
>  - basic working with minor issues during tests
> RFC v1:
>  - inital revision

Not need to resend your patch set for this, but when a patch set has
multiple patches and the changelog covers all the patches, the
changelog is expected to be in a cover letter separated from the
patches themselves.

For this patch:

Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

> +ifeq ($(BR2_PACKAGE_TI_GFX),y)
> +POWERVR_DEPENDENCIES += ti-gfx
> +endif

Technically, this part should have been in the next patch, because when
only 1/3 is applied, the ti-gfx package isn't there yet. But ok, we
don't care too much.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-07-12 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 14:34 [Buildroot] [PATCH v5 1/3] powervr: add powervr virtual package Spenser Gilliland
2013-07-12 14:34 ` [Buildroot] [PATCH v5 2/3] ti-gfx: add new package Spenser Gilliland
2013-07-13 14:11   ` Thomas Petazzoni
2013-07-13 17:08     ` Spenser Gilliland
2013-07-13 17:14       ` Thomas Petazzoni
2013-07-15 20:18   ` Peter Korsgaard
2013-07-15 21:12     ` Spenser Gilliland
2013-07-15 21:18       ` Peter Korsgaard
2013-07-12 14:34 ` [Buildroot] [PATCH v5 3/3] qt: add powervr and opengl Spenser Gilliland
2013-07-13 14:13   ` Thomas Petazzoni
2013-07-13 16:24     ` Spenser Gilliland
2013-07-13 17:27       ` Thomas Petazzoni
2013-07-15 21:21   ` Peter Korsgaard
2013-07-12 16:19 ` Thomas Petazzoni [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=20130712181907.1d514e82@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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