From: Michael Riesch <michael.riesch@wolfvision.net>
To: barebox@lists.infradead.org
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: [PATCH master 0/3] Fixes for WolfVision board code library and PF5 mainboard code
Date: Wed, 15 May 2024 10:00:33 +0200 [thread overview]
Message-ID: <20240515-b4-pf5-fixup-v1-0-a58c8ec94f48@wolfvision.net> (raw)
Habidere,
This series is a follow-up to
https://lore.barebox.org/barebox/20240412-feature-wolfvision-pf5-v2-0-7e277cc8831b@wolfvision.net/
and fixes a few things. I tried to reply to said thread and announce a
v3, but I just found that this reply never hit the list for ... reasons.
Anyway, here are the fixes. Do you think they can be applied directly
to master?
Looking forward to your comments!
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
Michael Riesch (3):
arm: boards: add pr_fmt() prefix to wolfvision pf5 board code
common: boards: move dependencies to wolfvision board code library
common: boards: wolfvision: fix handling of overlays parameter
arch/arm/boards/wolfvision-pf5/board.c | 3 +++
arch/arm/mach-rockchip/Kconfig | 2 --
common/boards/Kconfig | 2 ++
common/boards/wolfvision/common.c | 5 ++++-
4 files changed, 9 insertions(+), 3 deletions(-)
---
base-commit: 593248cde35ddedcb27c0791c621e6a4403d7068
change-id: 20240515-b4-pf5-fixup-1c0f8b592313
Best regards,
--
Michael Riesch <michael.riesch@wolfvision.net>
next reply other threads:[~2024-05-15 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 8:00 Michael Riesch [this message]
2024-05-15 8:00 ` [PATCH master 1/3] arm: boards: add pr_fmt() prefix to wolfvision pf5 board code Michael Riesch
2024-05-15 8:00 ` [PATCH master 2/3] common: boards: move dependencies to wolfvision board code library Michael Riesch
2024-05-15 8:00 ` [PATCH master 3/3] common: boards: wolfvision: fix handling of overlays parameter Michael Riesch
2024-05-15 8:32 ` Michael Riesch
2024-05-15 9:14 ` Ahmad Fatoum
2024-05-15 10:28 ` Michael Riesch
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=20240515-b4-pf5-fixup-v1-0-a58c8ec94f48@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=barebox@lists.infradead.org \
/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