From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/4] Tinker board boot fix and Linux/U-Boot update
Date: Fri, 10 Feb 2023 23:34:51 +0100 [thread overview]
Message-ID: <20230210233451.3a3a2f9f@windsurf> (raw)
In-Reply-To: <20230104002113.1038775-1-giulio.benetti@benettiengineering.com>
On Wed, 4 Jan 2023 01:21:09 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Giulio Benetti (4):
> configs/asus_tinker_rk3288_defconfig: fix boot by prepending tpl to
> spl+u-boot
> board/asus/tinker: rename label linux-next to linux in extlinux.conf
> configs/asus_tinker_rk3288_defconfig: bump Linux to 6.1.2 and U-boot
> to 2022.10
> board/asus/tinker: add a note to readme.txt for power supply
Series applied with minor adjustements here and there, nothing major.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-02-10 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:21 [Buildroot] [PATCH 0/4] Tinker board boot fix and Linux/U-Boot update Giulio Benetti
2023-01-04 0:21 ` [Buildroot] [PATCH 1/4] configs/asus_tinker_rk3288_defconfig: fix boot by prepending tpl to spl+u-boot Giulio Benetti
2023-01-04 0:21 ` [Buildroot] [PATCH 2/4] board/asus/tinker: rename label linux-next to linux in extlinux.conf Giulio Benetti
2023-01-04 0:21 ` [Buildroot] [PATCH 3/4] configs/asus_tinker_rk3288_defconfig: bump Linux to 6.1.2 and U-boot to 2022.10 Giulio Benetti
2023-01-04 0:21 ` [Buildroot] [PATCH 4/4] board/asus/tinker: add a note to readme.txt for power supply Giulio Benetti
2023-02-10 22:34 ` Thomas Petazzoni via buildroot [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=20230210233451.3a3a2f9f@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jagan@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.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