From: Ralf Baechle <ralf@linux-mips.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-mips@linux-mips.org,
linux-sh@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
x86@kernel.org, linux-alpha@vger.kernel.org
Subject: Re: [PATCH 5/7] PCI: Remove unnecessary #includes of <asm/pci.h>
Date: Fri, 5 Jun 2015 10:08:36 +0200 [thread overview]
Message-ID: <20150605080836.GR26432@linux-mips.org> (raw)
In-Reply-To: <20150604214957.2399.66129.stgit@bhelgaas-glaptop2.roam.corp.google.com>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
prev parent reply other threads:[~2015-06-05 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150604214614.2399.5142.stgit@bhelgaas-glaptop2.roam.corp.google.com>
2015-06-04 21:49 ` [PATCH 4/7] PCI: Include <linux/pci.h>, not <asm/pci.h> Bjorn Helgaas
2015-06-04 21:49 ` [PATCH 5/7] PCI: Remove unnecessary #includes of <asm/pci.h> Bjorn Helgaas
2015-06-05 1:53 ` Simon Horman
2015-06-05 8:08 ` Ralf Baechle [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=20150605080836.GR26432@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bhelgaas@google.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).