Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Can Peng <pengcan@kylinos.cn>
Cc: davem@davemloft.net, mgross@linux.intel.com,
	mikex.healy@intel.com, daniele.alessandrelli@gmail.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: keembay - publish OF module alias for OCS AES/SM4
Date: Mon, 27 Jul 2026 10:33:19 +1000	[thread overview]
Message-ID: <amanT_iK3Pr_HFd0@gondor.apana.org.au> (raw)
In-Reply-To: <20260714131442.153699-1-pengcan@kylinos.cn>

On Tue, Jul 14, 2026 at 09:14:42PM +0800, Can Peng wrote:
> The Keem Bay OCS AES/SM4 driver has an OF match table wired to
> .of_match_table, but does not export the table with MODULE_DEVICE_TABLE().
> 
> Although the match table lives in keembay-ocs-aes-core.o, that object is
> part of the composite keembay-ocs-aes module.  Add the missing
> MODULE_DEVICE_TABLE(of, ...) entry so modpost can generate OF module alias
> information for OF based module autoloading.
> 
> This is a source-level fix.  It does not claim dynamic hardware
> reproduction; the evidence is the driver-owned match table, its use by the
> platform driver, and the missing module alias publication.
> 
> Fixes: 885743324513 ("crypto: keembay - Add support for Keem Bay OCS AES/SM4")
> Signed-off-by: Can Peng <pengcan@kylinos.cn>
> ---
>  drivers/crypto/intel/keembay/keembay-ocs-aes-core.c | 1 +
>  1 file changed, 1 insertion(+)

Patch applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2026-07-27  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 13:14 [PATCH] crypto: keembay - publish OF module alias for OCS AES/SM4 Can Peng
2026-07-27  0:33 ` Herbert Xu [this message]

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=amanT_iK3Pr_HFd0@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=daniele.alessandrelli@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=mikex.healy@intel.com \
    --cc=pengcan@kylinos.cn \
    /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