public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: E Shattow <e@freeshell.de>
Cc: u-boot@lists.denx.de, Leo Yu-Chi Liang <ycliang@andestech.com>,
	rick@andestech.com, hal.feng@starfivetech.com,
	jamie.gibbons@microchip.com
Subject: Re: [GIT PULL] u-boot-riscv/next
Date: Mon, 23 Mar 2026 14:07:56 -0600	[thread overview]
Message-ID: <20260323200756.GK502704@bill-the-cat> (raw)
In-Reply-To: <bb87214b-8b1a-428c-a339-2e632ebc2b15@freeshell.de>

[-- Attachment #1: Type: text/plain, Size: 5181 bytes --]

On Mon, Mar 23, 2026 at 12:20:02PM -0700, E Shattow wrote:
> Hi Tom,
> 
> There are some Fixes tags for master in this pull request applied to
> next and not yet applied to master, noted inline below.
> 
> On 3/16/26 23:01, Leo Yu-Chi Liang wrote:
> > Hi Tom,
> > 
> > The following changes since commit 841856ed9675b26ec517fdd00b5cc0aef8db508e:
> > 
> >   Merge patch series "Add PCIe Boot support for TI J784S4 SoC" (2026-03-16 08:24:18 -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 b51e59c8b34c780e28728bc0cb58783855c7ffbf:
> > 
> >   riscv: Add support for BeagleV-Fire (2026-03-17 11:39:18 +0800)
> > 
> > CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/29548
> > ----------------------------------------------------------------
> > - board: starfive: Add Xunlong OrangePi RV
> > - board: starfive: Add VisionFive 2 Lite
> > - board: beagle: Add BeagleV-Fire
> > ----------------------------------------------------------------
> > E Shattow (5):
> >       board: starfive: visionfive2: Add Orange Pi RV selection by product_id
> >       configs: starfive: Add Orange Pi RV to visionfive2
> >       doc: board: starfive: Add Xunlong OrangePi RV
> 
> >       doc: board: starfive: jh7110 common give build output dir by env not arg
> 
> commit 24662f698f5ad6f444e6dc437c0b5a932726a6ef
> Fixes: 8304f3226700 ("doc: board: starfive: update jh7110 common
> description")
> 
> >       doc: board: starfive: jh7110 common update OPENSBI build env reference
> 
> commit 1edeb52086c6e160d93d86386505e6cc6ce1457c
> Fixes: 8304f3226700 ("doc: board: starfive: update jh7110 common
> description")
> 
> > 
> > Hal Feng (7):
> >       eeprom: starfive: Simplify get_ddr_size_from_eeprom()
> 
> commit 6015c98be50f2fc571c294d2f2b0768212fb7e99
> Fixes: aea1bd95b61e ("eeprom: starfive: Enable ID EEPROM configuration")
> 
> >       eeprom: starfive: Correct get_pcb_revision_from_eeprom()
> 
> commit 78253aeeecdfea4c71779905ff2b400fa7400b1c
> Fixes: aea1bd95b61e ("eeprom: starfive: Enable ID EEPROM configuration")
> 
> >       eeprom: starfive: Support eeprom data format v3
> >       pcie: starfive: Add a optional power gpio support
> >       configs: visionfive2: Add VisionFive 2 Lite DT to OF_LIST
> >       board: starfive: spl: Support VisionFive 2 Lite
> >       board: starfive: visionfive2: Add VisionFive 2 Lite fdt selection
> > 
> > Jamie Gibbons (1):
> >       riscv: Add support for BeagleV-Fire
> > 
> >  arch/riscv/Kconfig                                 |   4 +
> >  arch/riscv/cpu/jh7110/spl.c                        |   2 +-
> >  arch/riscv/include/asm/arch-jh7110/eeprom.h        |  13 ++-
> >  board/beagle/beaglev_fire/Kconfig                  |  43 ++++++++
> >  board/beagle/beaglev_fire/MAINTAINERS              |   7 ++
> >  board/beagle/beaglev_fire/Makefile                 |   6 ++
> >  board/beagle/beaglev_fire/beaglev_fire.c           | 117 +++++++++++++++++++++
> >  board/starfive/visionfive2/spl.c                   |   6 ++
> >  board/starfive/visionfive2/starfive_visionfive2.c  |   4 +
> >  .../starfive/visionfive2/visionfive2-i2c-eeprom.c  |  64 ++++++-----
> >  configs/beaglev_fire_defconfig                     |  29 +++++
> >  configs/starfive_visionfive2_defconfig             |   2 +-
> >  doc/board/starfive/index.rst                       |   1 +
> >  doc/board/starfive/jh7110_common.rst               |  11 +-
> >  doc/board/starfive/orangepi_rv.rst                 |  35 ++++++
> >  drivers/pci/pcie_starfive_jh7110.c                 |   8 ++
> >  include/configs/beaglev_fire.h                     |  57 ++++++++++
> >  17 files changed, 375 insertions(+), 34 deletions(-)
> >  create mode 100644 board/beagle/beaglev_fire/Kconfig
> >  create mode 100644 board/beagle/beaglev_fire/MAINTAINERS
> >  create mode 100644 board/beagle/beaglev_fire/Makefile
> >  create mode 100644 board/beagle/beaglev_fire/beaglev_fire.c
> >  create mode 100644 configs/beaglev_fire_defconfig
> >  create mode 100644 doc/board/starfive/orangepi_rv.rst
> >  create mode 100644 include/configs/beaglev_fire.h
> > 
> >  Best regards,
> >  Leo
> 
> I note that there may be other authors' contributions applied to next
> with Fixes tags for master that are not part of this pull request, not
> highlighted in my reply here.

Thanks for looking at this. To be clear and to repeat what I said on
IRC, we don't have the formal process (nor tooling nor human backup)
that the linux kernel has about fixes tags and what they get applied to.
It's up to individual custodians to decide if a Fixes commit is worth
pushing to a pending release, once the next window is open, or holding
off for more testing, as it's not serious enough of a problem. That
means it's also up to a contributor to follow-up if they thought
something should really go to master instead (and custodians should be
uinsg b4 and b4 ty, so contributors know where something is applied,
once it is applied).

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-03-23 20:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  6:01 [GIT PULL] u-boot-riscv/next 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2024-10-28 12:25 Leo Liang
2024-10-28 15:20 ` Tom Rini
2024-10-29  9:35   ` Leo Liang
2024-10-29 13:01     ` Michal Simek
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=20260323200756.GK502704@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=jamie.gibbons@microchip.com \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.com \
    /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