All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary R Hook <ghook@amd.com>
To: <linux-crypto@vger.kernel.org>
Cc: "herbert@gondor.apana.org.au >> Herbert Xu"
	<herbert@gondor.apana.org.au>
Subject: Re: [cryptodev:master 56/59] warning: (RAPIDIO_DMA_ENGINE && ..) selects DMA_ENGINE which has unmet direct dependencies (DMADEVICES)
Date: Wed, 20 Apr 2016 09:57:16 -0500	[thread overview]
Message-ID: <571798CB.1000200@amd.com> (raw)
In-Reply-To: <201604201852.NtqZ4byz%fengguang.wu@intel.com>

On 04/20/2016 05:35 AM, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
> head:   21ec757d2dd8650f978d27ad53cb1fcca8bb5e2b
> commit: 58ea8abf490415c390e0cc671e875510c9b66318 [56/59] crypto: ccp - Register the CCP as a DMA resource
> config: i386-randconfig-x018-201616 (attached as .config)
> reproduce:
>          git checkout 58ea8abf490415c390e0cc671e875510c9b66318
>          # save the attached .config to linux build tree
>          make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
> warning: (RAPIDIO_DMA_ENGINE && SND_SOC_SH4_SIU && CRYPTO_DEV_CCP_DD) selects DMA_ENGINE which has unmet direct dependencies (DMADEVICES)

I have sent a separate patch that appears to fix the 3 krobot problems. 
Apologies if I do not have the protocol correct.

Gary

      reply	other threads:[~2016-04-20 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 10:35 [cryptodev:master 56/59] warning: (RAPIDIO_DMA_ENGINE && ..) selects DMA_ENGINE which has unmet direct dependencies (DMADEVICES) kbuild test robot
2016-04-20 14:57 ` Gary R Hook [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=571798CB.1000200@amd.com \
    --to=ghook@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --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.