All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Tom Lendacky <thomas.lendacky@amd.com>, Gary Hook <gary.hook@amd.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/2] crypto: ccp - Remove unnecessary includes
Date: Fri,  2 Aug 2019 18:20:10 -0500	[thread overview]
Message-ID: <20190802232013.15957-1-helgaas@kernel.org> (raw)

From: Bjorn Helgaas <bhelgaas@google.com>

CCP includes <linux/pci.h> many times unnecessarily.  Add a couple
DMA-related includes for dma_direction and dma_get_mask(), which were
previously included indirectly via <linux/pci.h>.  Then remove the
unnecessary includes of <linux/pci.h>.

Bjorn Helgaas (2):
  crypto: ccp - Include DMA declarations explicitly
  crypto: ccp - Remove unnecessary linux/pci.h include

 drivers/crypto/ccp/ccp-crypto.h    | 1 -
 drivers/crypto/ccp/ccp-dev-v3.c    | 1 -
 drivers/crypto/ccp/ccp-dev-v5.c    | 1 -
 drivers/crypto/ccp/ccp-dev.h       | 2 +-
 drivers/crypto/ccp/ccp-dmaengine.c | 1 +
 drivers/crypto/ccp/ccp-ops.c       | 1 -
 drivers/crypto/ccp/psp-dev.h       | 1 -
 drivers/crypto/ccp/sp-dev.h        | 1 -
 8 files changed, 2 insertions(+), 7 deletions(-)

-- 
2.22.0.770.g0f2c4a37fd-goog


             reply	other threads:[~2019-08-02 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 23:20 Bjorn Helgaas [this message]
2019-08-02 23:20 ` [PATCH 1/2] crypto: ccp - Include DMA declarations explicitly Bjorn Helgaas
2019-08-06 16:44   ` Gary R Hook
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=20190802232013.15957-1-helgaas@kernel.org \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=gary.hook@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.lendacky@amd.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.