public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH u-boot-marvell v2 00/12] Updates for Turris Mox
Date: Fri, 17 Aug 2018 13:10:33 +0200	[thread overview]
Message-ID: <0faf8e9d-ecee-052d-2ece-a19a0c08454b@denx.de> (raw)
In-Reply-To: <20180817105902.10692-1-marek.behun@nic.cz>

Hi Marek,

On 17.08.2018 12:58, Marek Behún wrote:
> This is second version of updates for Turris Mox.
> The first version was sent three months ago, on 16th May. Sorry :).
> It would be great if this got to 2018.09 release, but I will
> understand if it does not.

I'm afraid, but this will have to wait for the next merge window.
We're at RC2 and I'll be leaving for one week vacation tomorrow.
I'll try to review the patches later then.

Thanks,
Stefan

      parent reply	other threads:[~2018-08-17 11:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 10:58 [U-Boot] [PATCH u-boot-marvell v2 00/12] Updates for Turris Mox Marek Behún
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 01/12] phy: marvell: Support changing SERDES map in board file Marek Behún
2018-09-19 12:17   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 02/12] clk: armada-37xx-periph: Support changing clock parent and rate Marek Behún
2018-09-19 12:18   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 03/12] board: turris_mox: Fix watchdog macro name Marek Behún
2018-09-19 12:18   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 04/12] board: turris_mox: Fixup U-Boot's device tree if PCIe connected Marek Behún
2018-08-21 10:22   ` [U-Boot] [PATCH u-boot-marvell v3 " Marek Behún
2018-09-19 12:28     ` Stefan Roese
2018-09-19 12:19   ` [U-Boot] [PATCH u-boot-marvell v2 " Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 05/12] board: turris_mox: Enable PCI in defconfig Marek Behún
2018-09-19 12:20   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 06/12] board: turris_mox: Cosmetic restructurization Marek Behún
2018-09-19 12:22   ` Stefan Roese
2018-11-20  7:04     ` Stefan Roese
2018-11-20 11:24       ` Marek Behun
2018-11-20 11:27         ` Stefan Roese
2018-11-20 11:40           ` Marek Behun
2018-11-20 11:58             ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 07/12] board: turris_mox: Change SERDES map depending on module topology Marek Behún
2018-09-19 12:22   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 08/12] board: turris_mox: Check and configure modules Marek Behún
2018-09-19 12:23   ` Stefan Roese
2018-08-17 10:58 ` [U-Boot] [PATCH u-boot-marvell v2 09/12] board: turris_mox: Setup Linux's device tree before boot Marek Behún
2018-09-19 12:23   ` Stefan Roese
2018-08-17 10:59 ` [U-Boot] [PATCH u-boot-marvell v2 10/12] board: turris_mox: Add gpio command to defconfig Marek Behún
2018-09-19 12:24   ` Stefan Roese
2018-08-17 10:59 ` [U-Boot] [PATCH u-boot-marvell v2 11/12] arch/arm/dts: Update Turris Mox device tree Marek Behún
2018-09-19 12:24   ` Stefan Roese
2018-08-17 10:59 ` [U-Boot] [PATCH u-boot-marvell v2 12/12] arch/arm/mvebu: Support 1 GB version of Turris Mox Marek Behún
2018-09-19 12:25   ` Stefan Roese
2018-08-17 11:10 ` Stefan Roese [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=0faf8e9d-ecee-052d-2ece-a19a0c08454b@denx.de \
    --to=sr@denx.de \
    --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