[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240605-comply-cycling-d9bbc9a4c933@spud>
Date: Wed, 5 Jun 2024 19:42:54 +0100
From: Conor Dooley <conor@...nel.org>
To: linux-riscv@...ts.infradead.org,
Conor Dooley <conor@...nel.org>
Cc: Conor Dooley <conor.dooley@...rochip.com>,
Daire McNamara <daire.mcnamara@...rochip.com>,
Cyril Jean <cyril.jean@...rochip.com>,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v1 0/5] PolarFire SoC Auto Update design info support
From: Conor Dooley <conor.dooley@...rochip.com>
On Wed, 10 Apr 2024 12:58:03 +0100, Conor Dooley wrote:
> There's a document that is internally available that the author of the
> design info/overlay format stuff wrote about how it is composed and I
> need to go read it and make a version of it publicly available before
> this can be merged.
>
> While implementing the design info support, I found a few opportunities
> for cleaning up the code and fixed a bug that had been mentioned
> internally about failure cases printing success. The scope based cleanup
> stuff in particular is rather helpful for the drivers using the system
> services mailbox, so I'll roll that out to the other users soonTM.
>
> [...]
The document that 1/5 relied on has been published, so I've applied
these to riscv-firmware-for-next.
[1/5] firmware: microchip: support writing bitstream info to flash
https://git.kernel.org/conor/c/a2bf9dfe0090
[4/5] firmware: microchip: move buffer allocation into mpfs_auto_update_set_image_address()
https://git.kernel.org/conor/c/e277026b5e2d
And 5/5 too, a conflict resolution seems to have upset b4.
Thanks,
Conor.
Powered by blists - more mailing lists