mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ladislav Michl <oss-lists@triops.cz>
Subject: Re: [ptxdist] [APPLIED] cryptodev: move cryptodev kernel module to platform
Date: Mon,  9 Mar 2026 08:22:20 +0100	[thread overview]
Message-ID: <20260309072220.4088061-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <aZseaaVemMqQY-iT@lenoch>

Thanks, applied as 45e5b8c6ba4ebc48e282a373bc9f00b9b0bd89f4.

Michael

[sent from post-receive hook]

On Mon, 09 Mar 2026 08:22:20 +0100, Ladislav Michl <oss-lists@triops.cz> wrote:
> Signed-off-by: Ladislav Michl <ladis@triops.cz>
> Message-Id: <aZseaaVemMqQY-iT@lenoch>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/cryptodev.in b/platforms/cryptodev.in
> similarity index 89%
> rename from rules/cryptodev.in
> rename to platforms/cryptodev.in
> index f59d8f58cc88..59d4aa9f062c 100644
> --- a/rules/cryptodev.in
> +++ b/platforms/cryptodev.in
> @@ -1,4 +1,4 @@
> -## SECTION=core
> +## SECTION=platform_project_specific
>  
>  config CRYPTODEV
>  	tristate
> diff --git a/rules/cryptodev-api.in b/rules/cryptodev-api.in
> index 86af4ed2302a..10a42c46d116 100644
> --- a/rules/cryptodev-api.in
> +++ b/rules/cryptodev-api.in
> @@ -2,7 +2,6 @@
>  
>  config CRYPTODEV_API
>  	tristate
> -	select CRYPTODEV	if RUNTIME
>  	prompt "cryptodev API"
>  	help
>  	  API headers for Cryptodev-linux. This is needed to build
> diff --git a/rules/cryptodev-api.make b/rules/cryptodev-api.make
> index 606108bd97b1..762195278d2e 100644
> --- a/rules/cryptodev-api.make
> +++ b/rules/cryptodev-api.make
> @@ -18,6 +18,7 @@ CRYPTODEV_API_VERSION	= $(CRYPTODEV_VERSION)
>  CRYPTODEV_API_MD5	= $(CRYPTODEV_MD5)
>  CRYPTODEV_API		= cryptodev-api-$(CRYPTODEV_API_VERSION)
>  CRYPTODEV_API_SUFFIX	= tar.gz
> +CRYPTODEV_API_PATCHES	= $(CRYPTODEV)
>  CRYPTODEV_API_URL	= $(CRYPTODEV_URL)
>  CRYPTODEV_API_SOURCE	= $(CRYPTODEV_SOURCE)
>  CRYPTODEV_API_DIR	= $(BUILDDIR)/$(CRYPTODEV_API)



  reply	other threads:[~2026-03-09  7:22 UTC|newest]

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

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=20260309072220.4088061-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=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