From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/11] Add BF60x processor support to Blackfin architecture.
Date: Fri, 1 Mar 2013 09:16:03 -0500 [thread overview]
Message-ID: <5130B823.1030007@ti.com> (raw)
In-Reply-To: <CAJxxZ0MXkj6wnrEpfyrYAi5CXr0j=ndKtZLU0meF4+t+S8dG0Q@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/28/2013 09:10 PM, Sonic Zhang wrote:
> Hi Tom,
>
> On Fri, Mar 1, 2013 at 5:22 AM, Tom Rini <trini@ti.com> wrote:
>> On Thu, Feb 21, 2013 at 07:06:38PM +0800, Sonic Zhang wrote:
>>
>>> From: Sonic Zhang <sonic.zhang@analog.com>
>>>
>>>
>>> ADSP-BF60x is the new generation Blackfin?? dual-core processor
>>> announced by Analog Devices in late March, 2012. This patch set
>>> adds BF60x processor support to Das U-Boot Blackfin
>>> architecture.
>>>
>>> For more information, see http://blackfin.uclinux.org .
>>>
>>> Changes in v4: - Remove last blank line in initcode.c. - Fix
>>> all checkpatch issues except for cpu name bf609-0.0. It is use
>>> as the link flags and is not an error. - Remove the values for
>>> variables in bf609 config headers whose values are useless. -
>>> Fix checkpatch warning whitespace before semicolon
>>
>> This all looks fine. If no one else comments soon, feel free to
>> make up your first pull request.
>>
>
> Thank you for your help. Because the Merge Window for the next
> release (v2013.04) was closed on Feb 09, should I make up the pull
> request after the (v2013.04) release on Apr. 15?
The merge window is for v1 of patches to be posted (unlike the
kernel), and I see v1 was Feb 07, so this is fine for the v2013.04
release.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRMLgiAAoJENk4IS6UOR1WYdIQAK6GxbyOksTxozrGI4/QHNc+
+94v4D2tw0PSaNPbaVodR5eL7U9YCIPIXStDvu56DNauF+UW8ZTA2NinJaL+NP92
XfkfGADBSXB9DK7/ZYdgxeF/MA0cF9mQuO56c6ZVXkBBAXrsNc+NdDuacQC77GdE
8h4kofuVk32ycPW3jZWXQL2esNx5wiux0sEcQ7CRyDS9KGjRuPUXF7C8JBRSon7Q
O9cuqxiX/Hc224xNu4w7KyIFqu3MNnQi7DTSXGwxT8mqXYJTgqpWqDBwisJX+oKP
7P9Tsd2f3ZcZLuLYC4LNstuN3si/6VPOfKaUI52+IJG+v1ZtHeKbZWQ0uSwe3Vfx
cKXmmyzNcOxb28Zk7y5OyISi/W9gld4Sa/wiUKFitD2Y7/ZMdX8I63oVi4kWgwyW
ox9UH+mUFj92edjyPflgRmMOFrGnNEBpJEKRJBWGztKCRR66QuSlOpQ+PebLuiPE
NYDuAh1w0PsgR1AZFHEQh+bt9q/GZn93mKZD6bbdIGcSn84g4GoenlxA6SPZ7Pwg
aXZ8LeU5cf3A8R4a6hnew87W4JgZ31mJ0u2sT9R2nv3m8frYb+UPCdhBItDV2oM7
t2PfAQPneZDkl4XcTi2QiQf+WtlMltJpi4yXRfrv/UU8v1ebW8KU1+acXieOMaT8
rmYIEiORyrcH/Hb/wH+4
=BLr9
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-03-01 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 11:06 [U-Boot] [PATCH v4 0/11] Add BF60x processor support to Blackfin architecture Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 01/11] blackfin: bf60x: new processor header files Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 02/11] blackfin: bf60x: Port blackfin core architecture code to boot on bf60x Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 03/11] blackfin: bf60x: add serial support Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 04/11] blackfin: bf60x: add dma support Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 05/11] blackfin: bf60x: support big cplb page Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 06/11] blackfin: bf60x: add gpio support Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 07/11] blackfin: bf60x: add board and headers files to support bf609 Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 08/11] blackfin: bf60x: add rsi/sdh support Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 09/11] blackfin: add bf6xx spi driver Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 10/11] blackfin: bf60x: add hw watchdog support Sonic Zhang
2013-02-21 11:06 ` [U-Boot] [PATCH v4 11/11] blackfin: bf60x: add resume from hibernate Sonic Zhang
2013-02-28 21:22 ` [U-Boot] [PATCH v4 0/11] Add BF60x processor support to Blackfin architecture Tom Rini
2013-03-01 2:10 ` Sonic Zhang
2013-03-01 14:16 ` Tom Rini [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=5130B823.1030007@ti.com \
--to=trini@ti.com \
--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.