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 1/1] package/libdvbcsa: fix altivec problems on powerpc64
Date: Mon, 28 Nov 2016 09:21:48 +0100	[thread overview]
Message-ID: <20161128092148.28b85791@free-electrons.com> (raw)
In-Reply-To: <cc3828a9d6d9dd16bd129e033e2463de8afcac04.1480311945.git.sam.bobroff@au1.ibm.com>

Hello,

On Mon, 28 Nov 2016 16:45:52 +1100, Sam Bobroff wrote:
> Fixes:
> http://autobuild.buildroot.net/results/e6d22f5e0258c7ebb8a3ed39c11e014c721cd219
> 
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
> ---
> Notes:
> 
> I'm not an expert on Altivec, but the fix seems reasonable and the
> package's test programs succeed.
> 
>  package/libdvbcsa/0001-altivec-powerpc64.patch | 26 ++++++++++++++++++++++++++
>  package/libdvbcsa/libdvbcsa.mk                 |  1 +
>  2 files changed, 27 insertions(+)
>  create mode 100644 package/libdvbcsa/0001-altivec-powerpc64.patch
> 
> diff --git a/package/libdvbcsa/0001-altivec-powerpc64.patch b/package/libdvbcsa/0001-altivec-powerpc64.patch
> new file mode 100644
> index 0000000..9a3c91a
> --- /dev/null
> +++ b/package/libdvbcsa/0001-altivec-powerpc64.patch

Patches should have a description + Signed-off-by. Also, please make
sure to submit this patch upstream. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-28  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  5:45 [Buildroot] [PATCH 1/1] package/libdvbcsa: fix altivec problems on powerpc64 Sam Bobroff
2016-11-28  8:21 ` Thomas Petazzoni [this message]
2016-11-28 22:39   ` Sam Bobroff

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=20161128092148.28b85791@free-electrons.com \
    --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