From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] Microblaze bug-fixes
Date: Wed, 16 Oct 2013 20:20:15 +0200 [thread overview]
Message-ID: <525ED8DF.2000306@monstr.eu> (raw)
In-Reply-To: <20131016134223.GG30016@bill-the-cat>
On 10/16/2013 03:42 PM, Tom Rini wrote:
> On Wed, Oct 16, 2013 at 09:06:30AM +0200, Michal Simek wrote:
>
>> Hi Tom,
>>
>> I have just found that there are two problems in microblaze compilation.
>> Also I have found that my regular testing is broken that's why I haven't
>> found these problems earlier.
>> Would it be possible to add these two patches to your tree.
>> I know it is late but still v2013.10 hasn't been tagged.
>
> Applied to u-boot/master, thanks!
Thanks a lot,
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/20131016/a6c6fbaa/attachment.pgp>
prev parent reply other threads:[~2013-10-16 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 7:06 [U-Boot] [PATCH 0/2] Microblaze bug-fixes Michal Simek
2013-10-16 7:06 ` [U-Boot] [PATCH 1/2] common: fsl: Fix broken SPDX-License-Identifier change Michal Simek
2013-10-16 7:06 ` [U-Boot] [PATCH 2/2] microblaze: Fix watchdog initialization Michal Simek
2013-10-16 13:42 ` [U-Boot] [PATCH 0/2] Microblaze bug-fixes Tom Rini
2013-10-16 18:20 ` Michal Simek [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=525ED8DF.2000306@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox