mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/3] cryptodev update
Date: Sun, 22 Feb 2026 16:17:30 +0100	[thread overview]
Message-ID: <aZseChqY58Wcw65n@lenoch> (raw)

A small update of cryptodev package consisting of one imported fix
from upstream and most importantly moving package to platform.
I guess it should be alway done this way. Cryptodev is linux module
and should depend on Linux kernel, however it currently depends on
Linux kernel tools (unfortunately both are using PTXCONF_KERNEL
symbol, so it remained unnoticed)

Ladislav Michl (3):
  cryptodev: fix compilation with Linux-6.18-rc1
  cryptodev: move cryptodev kernel module to platform
  cryptodev: simplify rules

 .../0004-Fix-build-for-Linux-6.18-rc1.patch   | 50 +++++++++++++++++++
 patches/cryptodev-linux-1.14/series           |  3 +-
 {rules => platforms}/cryptodev.in             |  2 +-
 rules/cryptodev-api.in                        |  1 -
 rules/cryptodev-api.make                      |  1 +
 rules/cryptodev.make                          |  9 ++--
 6 files changed, 57 insertions(+), 9 deletions(-)
 create mode 100644 patches/cryptodev-linux-1.14/0004-Fix-build-for-Linux-6.18-rc1.patch
 rename {rules => platforms}/cryptodev.in (89%)

-- 
2.47.3




             reply	other threads:[~2026-02-22 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 15:17 Ladislav Michl [this message]
2026-02-22 15:18 ` [ptxdist] [PATCH 1/3] cryptodev: fix compilation with Linux-6.18-rc1 Ladislav Michl
2026-02-22 15:19 ` [ptxdist] [PATCH 2/3] cryptodev: move cryptodev kernel module to platform Ladislav Michl
2026-02-22 15:19 ` [ptxdist] [PATCH 3/3] cryptodev: simplify rules Ladislav Michl

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=aZseChqY58Wcw65n@lenoch \
    --to=oss-lists@triops.cz \
    --cc=ptxdist@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