From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Julian Vetter <jvetter@kalrayinc.com>
Cc: Yann Sionneau <ysionneau@kalrayinc.com>
Subject: Re: [PATCH 1/2] kvx: Split sfr definition for kv3-1 and kv3-2
Date: Wed, 23 Oct 2024 14:45:44 +0200 [thread overview]
Message-ID: <172968754492.3883549.17547408594798949940.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241023085432.1593840-1-jvetter@kalrayinc.com>
On Wed, 23 Oct 2024 10:54:31 +0200, Julian Vetter wrote:
> On kv3-2 some SFR numbers have changed, were added and/or indexes within
> certain SFRs have changed. So, split the file in two, one for kv3-1 and
> one for kv3-2.
>
>
Applied, thanks!
[1/2] kvx: Split sfr definition for kv3-1 and kv3-2
https://git.pengutronix.de/cgit/barebox/commit/?id=977c2c0f1dc8 (link may not be stable)
[2/2] kvx: Request additional owner bit-fields on CV2
https://git.pengutronix.de/cgit/barebox/commit/?id=f4912a43991a (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-10-23 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 8:54 Julian Vetter
2024-10-23 8:54 ` [PATCH 2/2] kvx: Request additional owner bit-fields on CV2 Julian Vetter
2024-10-23 12:45 ` 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=172968754492.3883549.17547408594798949940.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--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