diff options
| author | Tom Rini <[email protected]> | 2026-05-12 15:41:52 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2026-05-12 15:41:52 -0600 |
| commit | e3e651c480c46b332f16a7555b97c6c6fd640a40 (patch) | |
| tree | 01f7277b103a10ef301e6981d7f4ca2e33f653db /test/py/tests/test_fit_auto_signed.py | |
| parent | 5732bd0f457b4c671e46574d64d4acb099c0f0a5 (diff) | |
| parent | 8d209186a1e4aca4ec44745d05d51de7e80f7e3e (diff) | |
Merge patch series "add memdup_nul(), use it and memdup() in a few places"next
Rasmus Villemoes <[email protected]> says:
There are quite a few places where we allocate X+1 bytes, initialize
the first X bytes via memcpy() and then set the last byte to 0.
The kernel has a helper for that, kmemdup_nul(). Introduce a similar
one, and start making use of it in a few places. Also the existing
memdup() helper can be put to more use.
There are lots more places one could modify. But for code shared with
host tools, one would need to do some refactoring, putting memdup()
and memdup_nul() in their own str-util.c TU which could then also be
included in the tools build.
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'test/py/tests/test_fit_auto_signed.py')
0 files changed, 0 insertions, 0 deletions
