netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <lkp@intel.com>, Breno Leitao <leitao@debian.org>
Cc: horia.geanta@nxp.com, pankaj.gupta@nxp.com, gaurav.jain@nxp.com,
	linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
	horms@kernel.org, linux-kernel@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: Re: [PATCH net-next v2 1/3] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST
Date: Mon, 1 Jul 2024 13:55:21 -0700	[thread overview]
Message-ID: <20240701135521.3ba809bb@kernel.org> (raw)
In-Reply-To: <202407011309.cpTuOGdg-lkp@intel.com>

On Mon, 1 Jul 2024 13:48:21 +0800 kernel test robot wrote:
> >> drivers/crypto/caam/ctrl.c:83:34: warning: 'imx8m_machine_match' defined but not used [-Wunused-const-variable=]  
>       83 | static const struct of_device_id imx8m_machine_match[] = {
>          |                            

Reading 5762c20593b6b95 it seems like hiding the references in
intentional. You gotta wrap this array in an ifdef for non-OF 
builds it seems.

  reply	other threads:[~2024-07-01 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 16:14 [PATCH net-next v2 0/3] crypto: caam: Unembed net_dev Breno Leitao
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 [this message]
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=20240701135521.3ba809bb@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gaurav.jain@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=horms@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).