From: Leo Liang <ycliang@andestech.com>
To: Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>
Subject: Re: [GIT PULL] u-boot-riscv/next
Date: Tue, 29 Oct 2024 17:35:04 +0800 [thread overview]
Message-ID: <ZyCr3a8I52q1gkfZ@swlinux02> (raw)
In-Reply-To: <20241028152010.GP4959@bill-the-cat>
Hi Tom,
On Mon, Oct 28, 2024 at 09:20:10AM -0600, Tom Rini wrote:
> [EXTERNAL MAIL]
> Date: Mon, 28 Oct 2024 09:20:10 -0600
> From: Tom Rini <trini@konsulko.com>
> To: Leo Liang <ycliang@andestech.com>
> Cc: u-boot@lists.denx.de, rick@andestech.com
> Subject: Re: [GIT PULL] u-boot-riscv/next
>
> On Mon, Oct 28, 2024 at 08:25:55PM +0800, Leo Liang wrote:
> > Hi Tom,
> >
> > The following changes since commit 28dc47038edc4e93f32d75a357131bcf01a18d85:
> >
> > Merge branch 'u-boot-nand-20241005' of https://gitlab.denx.de/u-boot/custodians/u-boot-nand-flash into next (2024-10-05 11:19:24 -0600)
> >
> > are available in the Git repository at:
> >
> > https://source.denx.de/u-boot/custodians/u-boot-riscv.git next
> >
> > for you to fetch changes up to f07daa5967f65771f90221ee9bfad9814e549647:
> >
> > riscv: mbv: Align DT with QEMU (2024-10-28 17:49:25 +0800)
> >
> > CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/23049
> >
> > ----------------------------------------------------------------
> > Michal Simek (1):
> > riscv: mbv: Align DT with QEMU
> >
> > arch/riscv/dts/xilinx-mbv32.dts | 30 ++++++++++--------------------
> > board/xilinx/mbv/Kconfig | 6 +++---
> > configs/xilinx_mbv32_defconfig | 12 ++++++------
> > 3 files changed, 19 insertions(+), 29 deletions(-)
>
> Why is this for -next and not master? We're not so far in to the cycle
> that next is open, and this seems clear enough to pull in today. Thanks.
>
> --
> Tom
Michal said that this patch might have to wait for its counterpart in QEMU be merged.
(https://lore.kernel.org/all/20241017072507.4033413-1-sai.pavan.boddu@amd.com/)
But like you said, this seems clear enough for master. I will create another PR for this patch.
Thanks!
Best regards,
Leo
next prev parent reply other threads:[~2024-10-29 9:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 12:25 [GIT PULL] u-boot-riscv/next Leo Liang
2024-10-28 15:20 ` Tom Rini
2024-10-29 9:35 ` Leo Liang [this message]
2024-10-29 13:01 ` Michal Simek
-- strict thread matches above, loose matches on Subject: below --
2026-03-17 6:01 Leo Yu-Chi Liang
2026-03-18 17:05 ` Tom Rini
2026-03-23 19:20 ` E Shattow
2026-03-23 20:07 ` Tom Rini
2026-03-13 2:06 [GIT,PULL] u-boot-riscv/next Leo Liang
2026-03-13 16:52 ` Tom Rini
2026-03-13 22:59 ` E Shattow
2026-03-16 12:23 ` Leo Liang
2025-12-08 6:19 [GIT PULL] u-boot-riscv/next Leo Liang
2025-12-08 22:09 ` Tom Rini
2025-09-20 10:20 [GIT,PULL] u-boot-riscv/next Leo Liang
2025-09-20 17:47 ` Tom Rini
2025-09-25 2:07 ` E Shattow
2025-09-25 3:39 ` E Shattow
2025-09-25 4:57 ` Yao Zi
2025-09-25 6:36 ` E Shattow
2025-07-03 14:09 [GIT PULL] u-boot-riscv/next Leo Liang
2025-07-03 16:29 ` Tom Rini
2025-03-25 10:55 Leo Liang
2025-03-25 20:17 ` Tom Rini
2024-12-18 7:49 Leo Liang
2024-12-18 17:40 ` Tom Rini
2023-12-28 5:38 Leo Liang
2023-12-28 16:55 ` Tom Rini
2023-12-18 11:44 Leo Liang
2023-12-18 16:59 ` 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=ZyCr3a8I52q1gkfZ@swlinux02 \
--to=ycliang@andestech.com \
--cc=rick@andestech.com \
--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