From: Johannes Zink <j.zink@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: patchwork-jzi@pengutronix.de,
Barebox Mailing List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2] crypto: crc32: make crc32 available in PBL
Date: Tue, 5 Sep 2023 14:27:50 +0200 [thread overview]
Message-ID: <8b79c33c-95be-d24f-c144-0a8aed460927@pengutronix.de> (raw)
In-Reply-To: <20230905122636.GM189379@pengutronix.de>
On 9/5/23 14:26, Sascha Hauer wrote:
> On Tue, Sep 05, 2023 at 09:57:21AM +0200, Johannes Zink wrote:
>> Hi Sascha,
>>
>> On 9/4/23 10:19, Sascha Hauer wrote:
>>> On Tue, Aug 29, 2023 at 04:38:32PM +0200, Johannes Zink wrote:
>>>> crc32 may be required in PBL for checking data integrity. Add it to PBL
>>>> when CONFIG_CRC32 is enabled.
>>>>
>>>> To save some memory use a slower-but-smaller variant of the crc32 algorithm
>>>> in the PBL.
>>>
>>> I've just sent an alternative patch series. Please check if that works
>>> for you.
>>
>> What did you base the series on? Maybe I am holding it wrong, but it does
>> neither apply on v2023.07.1 which I use in my customer project nor on
>> upstream/next.
>
> It's already included in next. I had to re-order the patches though
> because my original order caused some compile failures in between.
>
I see, thanks. I will pick and test the patches on my customer hardware in the
next few days.
Johannes
> Sascha
>
>
--
Pengutronix e.K. | Johannes Zink |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686| Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-09-05 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 14:38 Johannes Zink
2023-08-29 15:00 ` Ahmad Fatoum
2023-09-04 8:19 ` Sascha Hauer
2023-09-05 7:57 ` Johannes Zink
2023-09-05 12:26 ` Sascha Hauer
2023-09-05 12:27 ` Johannes Zink [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=8b79c33c-95be-d24f-c144-0a8aed460927@pengutronix.de \
--to=j.zink@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=patchwork-jzi@pengutronix.de \
--cc=sha@pengutronix.de \
/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