Re: [PATCH v2 0/8] odb: unify read and write streams

Karthik Nayak <[email protected]>
Newsgroups org.kernel.vger.git
Message-ID <CAOLa=ZTtn4kpQq6H8gJpEnC9RRbb=eFgKjxGEQyeJGYr5CcW2Q@mail.gmail.com>
Patrick Steinhardt <[email protected]> writes:

> Hi,
>
> we have two different kind of object database streams in our code base:
> `odb_write_stream` and `odb_read_stream`. While those are used for
> different use cases, the provided functionality is ultimately the exact
> same.
>
> This patch series thus refactors these streams so that we have a single
> `odb_stream`, only. This allows us to reuse the streams for different
> kinds of purposes and makes them more generally useful overall. For
> example, it's trivially possible now to create an object stream for any
> given object and then write that stream into a different source.
>
> The series is built on top of 5b2471720c (The 10th batch, 2026-08-03).
>
> Changes in v2:
>   - Use the correct object type when hashing in-memory objects.
>   - Remove a stale comment.
>   - Adapt a commit message to mention that renames will follow in
>     subsequent commits.
>   - Add another commit to rename `struct input_zstream_data`.
>   - Link to v1: https://patch.msgid.link/[email protected]
>

I went through v2 and I think its already in a good state!
signature.asc (application/pgp-signature, 690 B)
-----BEGIN PGP SIGNATURE-----

iQHKBAEBCgA0FiEEV85Mf2N1cQ/LZcYGPtWfJI5GjH8FAmp69a8WHGthcnRoaWsu
MTg4QGdtYWlsLmNvbQAKCRA+1Z8kjkaMf9KhC/4rtVDbtbO9ysltpXJEQi+Xdfe9
FEPkHm1YoSFqLB/QZdqOjYItmety0PN58OnMow/0C0bu2iY1whPT1i0OAM8JE8fT
9O9+N0gaoRxYUkGEk0V5dc1sUbX6C1CRIQgUoUf6unXrrxAPg0kSOHuGT/fLcq2U
1YlvlLenUj5cpM5yRGZWUW6nAhcJUjFqtCKo1AgEDu9TPplcPQ2/uEkauTXD3nXb
flZZXFvw8vm1uZm5nDN4j9XmkQ3XQn6QhumXcnXdcRO370WlLs6psYX910MDJJS5
2OxWGhjcS1zvc0VF5/VTRVAHQ2TiCFPKKr9rFqhO6pObwLFZNVvx62wuyGetDoAh
/TGp3XC310Luv46LoRFMxsYPEODSlx9FvlEke1cK3AwNCbUtIO8modEvVWchG735
x6yIIGmtbaOiXprxmcXAcMd0Wpd5w+Tq6EiX7QuN4ptl0RzIS4aKy7qJdqi14odh
G6kGmXpxIBs1MwraglI+W5Yl/FyZrF4jurpUGVc=
=gvQT
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.