From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request - arm/zynq
Date: Thu, 07 Nov 2013 12:55:31 +0100 [thread overview]
Message-ID: <527B7FB3.301@monstr.eu> (raw)
In-Reply-To: <20131107105018.5bf39afa@lilith>
Hi Albert,
On 11/07/2013 10:50 AM, Albert ARIBAUD wrote:
> Hi Michal,
>
> On Wed, 06 Nov 2013 09:28:16 +0100, Michal Simek <monstr@monstr.eu>
> wrote:
>
>> Hi Albert,
>>
>> please pull these two patches to your arm next branch.
>> It depends on "zynq: Use arch_cpu_init() instead of lowlevel_init()"
>> (sha1: 262f08d6ea18a62f827b8ccb60f355ca2eaf6e2b) patch
>> which you have in your branch that's why I have rebased them
>> on the top.
>>
>> Thanks,
>> Michal
>
> Is this really for 'next' and not 'master'? IOW, do you really mean it
> *not* to go into 2014.01?
Every maintainer has different strategies for branches.
But anyway, I want to add these patches/fixes to the 2014.01.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131107/7f189bff/attachment.pgp>
next prev parent reply other threads:[~2013-11-07 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 7:36 [U-Boot] Pull request - arm/zynq v3 Michal Simek
2013-09-03 12:12 ` Albert ARIBAUD
2013-09-04 7:38 ` Michal Simek
2013-11-06 8:28 ` [U-Boot] Pull request - arm/zynq Michal Simek
2013-11-07 9:50 ` Albert ARIBAUD
2013-11-07 11:55 ` Michal Simek [this message]
2013-11-24 10:35 ` Albert ARIBAUD
-- strict thread matches above, loose matches on Subject: below --
2013-08-12 6:59 Michal Simek
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=527B7FB3.301@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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.