From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: Re: [PATCH master v2 0/3] Fixes for WolfVision board code library and PF5 mainboard code
Date: Thu, 16 May 2024 08:11:48 +0200 [thread overview]
Message-ID: <171583990820.2730688.10318615219155083728.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240515-b4-pf5-fixup-v2-0-7c2aff3f7465@wolfvision.net>
On Wed, 15 May 2024 12:35:54 +0200, Michael Riesch wrote:
> 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.
>
> [...]
Applied, thanks!
[1/3] arm: boards: add pr_fmt() prefix to wolfvision pf5 board code
https://git.pengutronix.de/cgit/barebox/commit/?id=cfde0d207cd3 (link may not be stable)
[2/3] common: boards: move dependencies to wolfvision board code library
https://git.pengutronix.de/cgit/barebox/commit/?id=adb7cbee7b31 (link may not be stable)
[3/3] common: boards: wolfvision: fix handling of overlays parameter
https://git.pengutronix.de/cgit/barebox/commit/?id=cc211bb091fc (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-05-16 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 10:35 Michael Riesch
2024-05-15 10:35 ` [PATCH master v2 1/3] arm: boards: add pr_fmt() prefix to wolfvision pf5 board code Michael Riesch
2024-05-15 10:35 ` [PATCH master v2 2/3] common: boards: move dependencies to wolfvision board code library Michael Riesch
2024-05-15 10:35 ` [PATCH master v2 3/3] common: boards: wolfvision: fix handling of overlays parameter Michael Riesch
2024-05-16 6:11 ` Sascha Hauer [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=171583990820.2730688.10318615219155083728.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
/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