mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gary R Hook <ghook@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"Hook, Gary" <Gary.Hook@amd.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 1/2] crypto: ccp - Include DMA declarations explicitly
Date: Tue, 6 Aug 2019 16:44:57 +0000	[thread overview]
Message-ID: <33e14857-a54f-1077-b9e4-c2945074a626@amd.com> (raw)
In-Reply-To: <20190802232013.15957-2-helgaas@kernel.org>

On 8/2/19 6:20 PM, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
> 
> ccp-dev.h uses dma_direction, which is defined in linux/dma-direction.h.
> Include that explicitly instead of relying on it being included via
> linux/pci.h, since ccp-dev.h requires nothing else from linux/pci.h.
> 
> Similarly, ccp-dmaengine.c uses dma_get_mask(), which is defined in
> linux/dma-mapping.h, so include that explicitly since it requires nothing
> else from linux/pci.h.
> 
> A future patch will remove the includes of linux/pci.h where it is not
> needed.
> 
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

Acked-by: Gary R Hook <gary.hook@amd.com>

> ---
>   drivers/crypto/ccp/ccp-dev.h       | 1 +
>   drivers/crypto/ccp/ccp-dmaengine.c | 1 +
>   2 files changed, 2 insertions(+)
> 
> diff --git a/drivers/crypto/ccp/ccp-dev.h b/drivers/crypto/ccp/ccp-dev.h
> index 5e624920fd99..89aee0900a06 100644
> --- a/drivers/crypto/ccp/ccp-dev.h
> +++ b/drivers/crypto/ccp/ccp-dev.h
> @@ -17,6 +17,7 @@
>   #include <linux/mutex.h>
>   #include <linux/list.h>
>   #include <linux/wait.h>
> +#include <linux/dma-direction.h>
>   #include <linux/dmapool.h>
>   #include <linux/hw_random.h>
>   #include <linux/bitops.h>
> diff --git a/drivers/crypto/ccp/ccp-dmaengine.c b/drivers/crypto/ccp/ccp-dmaengine.c
> index 7f22a45bbc11..f69d495873f0 100644
> --- a/drivers/crypto/ccp/ccp-dmaengine.c
> +++ b/drivers/crypto/ccp/ccp-dmaengine.c
> @@ -9,6 +9,7 @@
>   
>   #include <linux/module.h>
>   #include <linux/kernel.h>
> +#include <linux/dma-mapping.h>
>   #include <linux/dmaengine.h>
>   #include <linux/spinlock.h>
>   #include <linux/mutex.h>
> 


  reply	other threads:[~2019-08-06 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 23:20 [PATCH 0/2] crypto: ccp - Remove unnecessary includes Bjorn Helgaas
2019-08-02 23:20 ` [PATCH 1/2] crypto: ccp - Include DMA declarations explicitly Bjorn Helgaas
2019-08-06 16:44   ` Gary R Hook [this message]
2019-08-02 23:20 ` [PATCH 2/2] crypto: ccp - Remove unnecessary linux/pci.h include Bjorn Helgaas
2019-08-06 16:45   ` Gary R Hook
2019-08-09  6:20 ` [PATCH 0/2] crypto: ccp - Remove unnecessary includes Herbert Xu

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=33e14857-a54f-1077-b9e4-c2945074a626@amd.com \
    --to=ghook@amd.com \
    --cc=Gary.Hook@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=helgaas@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®