From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, jvetter@kalrayinc.com
Cc: ysionneau@kalrayinc.com, jborne@kalrayinc.com,
jhascoet@kalrayinc.com, clement@clement-leger.fr
Subject: Re: [PATCH 1/5] kvx: Fix barebox build for kvx
Date: Tue, 18 Jun 2024 08:13:45 +0200 [thread overview]
Message-ID: <171869122552.3822978.150489488503401465.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240617134329.3671762-2-jvetter@kalrayinc.com>
On Mon, 17 Jun 2024 15:43:25 +0200, jvetter@kalrayinc.com wrote:
> Add <linux/bug.h> to arch/kvx/lib/dma-default.c
>
>
Applied, thanks!
[1/5] kvx: Fix barebox build for kvx
https://git.pengutronix.de/cgit/barebox/commit/?id=c084e47d1764 (link may not be stable)
[2/5] kvx: Add 'stop' instruction to power down sequence
https://git.pengutronix.de/cgit/barebox/commit/?id=ec10ee14e3dd (link may not be stable)
[3/5] kvx: robustify i/d cache startup
https://git.pengutronix.de/cgit/barebox/commit/?id=7a2b1131307a (link may not be stable)
[4/5] kvx: handle syscalls gracefully
https://git.pengutronix.de/cgit/barebox/commit/?id=8586e67a013b (link may not be stable)
[5/5] kvx: add support for Coolidge V1/V2 march selection
https://git.pengutronix.de/cgit/barebox/commit/?id=115f47b183fb (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next prev parent reply other threads:[~2024-06-18 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 13:43 Update kvx support jvetter
2024-06-17 13:43 ` [PATCH 1/5] kvx: Fix barebox build for kvx jvetter
2024-06-18 6:13 ` Sascha Hauer [this message]
2024-06-17 13:43 ` [PATCH 2/5] kvx: Add 'stop' instruction to power down sequence jvetter
2024-06-17 13:43 ` [PATCH 3/5] kvx: robustify i/d cache startup jvetter
2024-06-17 13:43 ` [PATCH 4/5] kvx: handle syscalls gracefully jvetter
2024-06-17 13:43 ` [PATCH 5/5] kvx: add support for Coolidge V1/V2 march selection jvetter
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=171869122552.3822978.150489488503401465.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=clement@clement-leger.fr \
--cc=jborne@kalrayinc.com \
--cc=jhascoet@kalrayinc.com \
--cc=jvetter@kalrayinc.com \
--cc=ysionneau@kalrayinc.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