From: Tadeusz Struk <tadeusz.struk@intel.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
Date: Fri, 15 Apr 2016 13:39:28 -0700 [thread overview]
Message-ID: <57115180.3060009@intel.com> (raw)
In-Reply-To: <201604160353.56AsWSoq%fengguang.wu@intel.com>
On 04/15/2016 12:52 PM, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
> head: 5f575efea79caae69b81f922d99b221302a2c003
> commit: d6064165ba4449ea085a389724d728258a3180ec [43/49] crypto: qat - adf_dev_stop should not be called in atomic context
> config: i386-allmodconfig (attached as .config)
> reproduce:
> git checkout d6064165ba4449ea085a389724d728258a3180ec
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
>>> WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
> The function __init init_module() references
> a function __exit adf_exit_vf_wq().
> This is often seen when error handling in the init function
> uses functionality in the exit path.
> The fix is often to remove the __exit annotation of
> adf_exit_vf_wq() so it may be used outside an exit section.
>
Is it still complaining even after this?
https://patchwork.kernel.org/patch/8854461/
Thanks,
--
TS
prev parent reply other threads:[~2016-04-15 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 19:52 [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq() kbuild test robot
2016-04-15 20:39 ` Tadeusz Struk [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=57115180.3060009@intel.com \
--to=tadeusz.struk@intel.com \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
/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.