All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, horia.geanta@nxp.com, pankaj.gupta@nxp.com,
	gaurav.jain@nxp.com, linux-crypto@vger.kernel.org,
	horms@kernel.org, netdev@vger.kernel.org,
	herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] crypto: caam: Unembed net_dev
Date: Thu, 04 Jul 2024 18:00:29 +0000	[thread overview]
Message-ID: <172011602974.29043.12028718630944239259.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240702185557.3699991-1-leitao@debian.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  2 Jul 2024 11:55:50 -0700 you wrote:
> 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:
> v3:
> 	* Fix free_netdev() deference per-cpu (Simon)
> 	* Hide imx8m_machine_match under CONFIG_OF (Jakub)
> 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/
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/4] crypto: caam: Avoid unused imx8m_machine_match variable
    https://git.kernel.org/netdev/net-next/c/9b5c33b1a3b7
  - [net-next,v3,2/4] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST
    https://git.kernel.org/netdev/net-next/c/beba3771d9e0
  - [net-next,v3,3/4] crypto: caam: Unembed net_dev structure from qi
    https://git.kernel.org/netdev/net-next/c/82c81e740def
  - [net-next,v3,4/4] crypto: caam: Unembed net_dev structure in dpaa2
    https://git.kernel.org/netdev/net-next/c/0e1a4d427f58

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-07-04 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 18:55 [PATCH net-next v3 0/3] crypto: caam: Unembed net_dev Breno Leitao
2024-07-02 18:55 ` [PATCH net-next v3 1/4] crypto: caam: Avoid unused imx8m_machine_match variable Breno Leitao
2024-07-05 10:11   ` Horia Geanta
2024-07-08 11:29     ` Breno Leitao
2024-07-09 10:44       ` Horia Geanta
2024-07-02 18:55 ` [PATCH net-next v3 2/4] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST Breno Leitao
2024-07-02 18:55 ` [PATCH net-next v3 3/4] crypto: caam: Unembed net_dev structure from qi Breno Leitao
2024-07-04  2:45   ` Jakub Kicinski
2024-07-04 16:15     ` Breno Leitao
2024-07-04 17:18       ` Jakub Kicinski
2024-07-02 18:55 ` [PATCH net-next v3 4/4] crypto: caam: Unembed net_dev structure in dpaa2 Breno Leitao
2024-07-03  5:45   ` [EXT] " Gaurav Jain
2024-07-03 11:26     ` Breno Leitao
2024-07-04 18:00 ` patchwork-bot+netdevbpf [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=172011602974.29043.12028718630944239259.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.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=leitao@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.