U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Tom Rini <trini@konsulko.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Please pull u-boot-marvell/next
Date: Tue, 21 Dec 2021 09:27:09 +0100	[thread overview]
Message-ID: <f15af4ac-cee4-97c0-0ff6-39cb5eda4756@denx.de> (raw)

Hi Tom,

please pull the following Marvell MVEBU related patches into next:

----------------------------------------------------------------
- pci_mvebu: Misc improvements and cleanup (Pali)
- turris_mox: Remove extra newline after module topology (Marek)
----------------------------------------------------------------

Here the Azure build, without any issues:

https://dev.azure.com/sr0718/u-boot/_build/results?buildId=142&view=results

Thanks,
Stefan



The following changes since commit 4afab30caea3211032710c4298a8839d3254e7f7:

   Merge tag 'v2022.01-rc4' into next (2021-12-20 17:12:04 -0500)

are available in the Git repository at:

   git@source.denx.de:u-boot/custodians/u-boot-marvell.git next

for you to fetch changes up to 6488939b4a78e03999c15314bed358b4e26940d0:

   arm: mvebu: turris_mox: Remove extra newline after module topology 
(2021-12-21 07:42:01 +0100)

----------------------------------------------------------------
Marek Behún (1):
       arm: mvebu: turris_mox: Remove extra newline after module topology

Pali Rohár (3):
       pci: pci_mvebu: Move setup for BAR[0] where other BARs are setup
       pci: pci_mvebu: Replace MBUS_PCI_*_SIZE by resource_size()
       pci: pci_mvebu: Remove unused DECLARE_GLOBAL_DATA_PTR

  board/CZ.NIC/turris_mox/turris_mox.c |  3 ---
  drivers/pci/pci_mvebu.c              | 27 +++++++++++++--------------
  2 files changed, 13 insertions(+), 17 deletions(-)

             reply	other threads:[~2021-12-21  8:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  8:27 Stefan Roese [this message]
2021-12-23  1:55 ` Please pull u-boot-marvell/next Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2026-06-10 12:21 Stefan Roese
2026-06-10 19:59 ` Tom Rini
2023-03-30  8:22 Stefan Roese
2023-03-30 14:35 ` Tom Rini
2023-03-24 14:49 Stefan Roese
2023-03-25 13:39 ` Tom Rini
2023-03-01 15:49 Stefan Roese
2023-03-01 19:54 ` Tom Rini
2022-09-20  6:59 Stefan Roese
2022-09-20 18:16 ` Tom Rini
2021-12-18 13:51 Stefan Roese
2021-12-18 14:12 ` Tom Rini
2021-10-01 12:36 Stefan Roese
2021-10-01 13:16 ` Tom Rini

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=f15af4ac-cee4-97c0-0ff6-39cb5eda4756@denx.de \
    --to=sr@denx.de \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox