All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] libnspr: add microblaze support
Date: Fri, 10 Jan 2014 07:36:41 +0800	[thread overview]
Message-ID: <20140110073641.60e41ea3@skate> (raw)
In-Reply-To: <52CED554.20103@mind.be>

Dear Arnout Vandecappelle,

On Thu, 09 Jan 2014 17:59:00 +0100, Arnout Vandecappelle wrote:

>   Maybe it's better to add this as a separate patch rather than updating 
> the existing patch. That will make it slightly easier to track upstream 
> if either of these is ever accepted there.

Fully agreed. Microblaze and NIOS II support should be in separate
patches.

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

  reply	other threads:[~2014-01-09 23:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 16:33 [Buildroot] [PATCH 0/4] Microblaze Autobuilder Fixes Spenser Gilliland
2014-01-08 16:33 ` [Buildroot] [PATCH 1/4] gdb: use consistent version on host and target for microblaze and arc Spenser Gilliland
2014-01-09 23:35   ` Thomas Petazzoni
2014-01-08 16:33 ` [Buildroot] [PATCH 2/4] libnspr: add microblaze support Spenser Gilliland
2014-01-09 16:59   ` Arnout Vandecappelle
2014-01-09 23:36     ` Thomas Petazzoni [this message]
2014-01-08 16:33 ` [Buildroot] [PATCH 3/4] libsigsegv: fix for microblaze Spenser Gilliland
2014-01-09 23:37   ` Thomas Petazzoni
2014-01-14 22:34   ` Peter Korsgaard
2014-01-08 16:33 ` [Buildroot] [PATCH 4/4] pixman: do not build demos or tests Spenser Gilliland
2014-01-09 23:40   ` Thomas Petazzoni

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=20140110073641.60e41ea3@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 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.