From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1
Date: Wed, 28 May 2014 16:47:55 +0200 [thread overview]
Message-ID: <20140528164755.2568e568@free-electrons.com> (raw)
In-Reply-To: <CAEBucnAmLn1C7zVevhPL+e4sJybWXadQrd8prr8a68=+BN6e-A@mail.gmail.com>
Dear Spenser Gilliland,
On Wed, 28 May 2014 09:45:25 -0500, Spenser Gilliland wrote:
> > Did you look at Waldemar patches? He upgraded quite a few components of
> > the Microblaze toolchains. It would be nice to not ping-pong between
> > patches proposed by you, and then patches proposed by Waldemar, and
> > then again by you. So please coordinate with Waldemar.
>
> The only patches from Waldemar appears to be
> http://patchwork.ozlabs.org/patch/343980/ . Were they not added to
> patchwork?
Waldemar patches have been applied, so they are no longer visible in
patchwork as 'New'.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-28 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 21:15 [Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1 Spenser Gilliland
2014-05-28 6:16 ` Thomas Petazzoni
2014-05-28 6:30 ` Spenser Gilliland
2014-05-28 6:43 ` Thomas Petazzoni
2014-05-28 14:20 ` Spenser Gilliland
2014-05-28 14:36 ` Thomas Petazzoni
2014-05-28 14:45 ` Spenser Gilliland
2014-05-28 14:47 ` Thomas Petazzoni [this message]
2014-05-28 15:03 ` Spenser Gilliland
2014-05-28 15:17 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-06-01 13:48 Javier Domingo Cansino
2014-06-01 15:26 ` Spenser Gilliland
2014-06-01 16:14 ` Javier Domingo Cansino
2014-06-01 16:52 ` Spenser Gilliland
2014-06-01 17:14 ` Javier Domingo Cansino
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=20140528164755.2568e568@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 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.