On (24/05/31 13:07), Herbert Xu wrote:
> On Mon, May 20, 2024 at 07:04:43PM +0800, Herbert Xu wrote:
> > This patch series adds an interface to set compression algorithm
> > parameters. The third patch is only an example. Each algorithm
> > could come up with its own distinct set of parameters and format
> > if necessary.
> >
> > Herbert Xu (3):
> > crypto: scomp - Add setparam interface
> > crypto: acomp - Add setparam interface
> > crypto: acomp - Add comp_params helpers
> >
> > crypto/acompress.c | 70 +++++++++++++++++--
> > crypto/compress.h | 9 ++-
> > crypto/scompress.c | 103 +++++++++++++++++++++++++++-
> > include/crypto/acompress.h | 41 ++++++++++-
> > include/crypto/internal/acompress.h | 3 +
> > include/crypto/internal/scompress.h | 37 ++++++++++
> > 6 files changed, 252 insertions(+), 11 deletions(-)
> >
> > --
> > 2.39.2
>
> So does this satsify your needs Sergey? I'm not going to apply this
> if you won't be using it.
Oh, I didn't see this series (not subscribed to linux-crypto).
Let me take a look.
On (24/05/31 14:12), Sergey Senozhatsky wrote:
> On (24/05/31 13:07), Herbert Xu wrote:
> > On Mon, May 20, 2024 at 07:04:43PM +0800, Herbert Xu wrote:
> > > This patch series adds an interface to set compression algorithm
> > > parameters. The third patch is only an example. Each algorithm
> > > could come up with its own distinct set of parameters and format
> > > if necessary.
> > >
> > > Herbert Xu (3):
> > > crypto: scomp - Add setparam interface
> > > crypto: acomp - Add setparam interface
> > > crypto: acomp - Add comp_params helpers
> > >
> > > crypto/acompress.c | 70 +++++++++++++++++--
> > > crypto/compress.h | 9 ++-
> > > crypto/scompress.c | 103 +++++++++++++++++++++++++++-
> > > include/crypto/acompress.h | 41 ++++++++++-
> > > include/crypto/internal/acompress.h | 3 +
> > > include/crypto/internal/scompress.h | 37 ++++++++++
> > > 6 files changed, 252 insertions(+), 11 deletions(-)
> > >
> > > --
> > > 2.39.2
> >
> > So does this satsify your needs Sergey? I'm not going to apply this
> > if you won't be using it.
>
> Oh, I didn't see this series (not subscribed to linux-crypto).
> Let me take a look.
Ah, wonderful. The series landed in the SPAM folder:
"Why is this message in spam? It is similar to messages that were
identified as spam in the past."
Whatever that means. Recovered, thanks for pinging me on this.