Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: kuba@kernel.org, horia.geanta@nxp.com, pankaj.gupta@nxp.com,
	gaurav.jain@nxp.com, linux-crypto@vger.kernel.org
Cc: horms@kernel.org, netdev@vger.kernel.org,
	herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org
Subject: [PATCH net-next v2 0/3] crypto: caam: Unembed net_dev
Date: Fri, 28 Jun 2024 09:14:45 -0700	[thread overview]
Message-ID: <20240628161450.2541367-1-leitao@debian.org> (raw)

This will un-embed the net_device struct from inside other struct, so we
can add flexible array into net_device.

This also enable COMPILE test for FSL_CAAM, as any config option that
depends on ARCH_LAYERSCAPE.

Changelog:
v2:
	* added a cover letter (Jakub)
	* dropped the patch that makes FSL_DPAA dependent of
	  COMPILE_TEST, since it exposes other problems.
v1:
	* https://lore.kernel.org/all/20240624162128.1665620-1-leitao@debian.org/


Breno Leitao (3):
  crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST
  crypto: caam: Unembed net_dev structure from qi
  crypto: caam: Unembed net_dev structure in dpaa2

 drivers/crypto/caam/Kconfig       |  2 +-
 drivers/crypto/caam/caamalg_qi2.c | 28 +++++++++++++++++---
 drivers/crypto/caam/caamalg_qi2.h |  2 +-
 drivers/crypto/caam/qi.c          | 43 +++++++++++++++++++++++++------
 4 files changed, 62 insertions(+), 13 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-06-28 16:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 16:14 Breno Leitao [this message]
2024-06-28 16:14 ` [PATCH net-next v2 1/3] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST Breno Leitao
2024-07-01  5:48   ` kernel test robot
2024-07-01 20:55     ` Jakub Kicinski
2024-07-02 17:53     ` Breno Leitao
2024-06-28 16:14 ` [PATCH net-next v2 2/3] crypto: caam: Unembed net_dev structure from qi Breno Leitao
2024-06-28 16:14 ` [PATCH net-next v2 3/3] crypto: caam: Unembed net_dev structure in dpaa2 Breno Leitao

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=20240628161450.2541367-1-leitao@debian.org \
    --to=leitao@debian.org \
    --cc=gaurav.jain@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pankaj.gupta@nxp.com \
    /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