linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Michal Simek <monstr@monstr.eu>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/7] microblaze/PCI: Remove unused declarations
Date: Mon, 8 Jun 2015 07:58:46 -0500	[thread overview]
Message-ID: <20150608125846.GV3631@google.com> (raw)
In-Reply-To: <55754D06.9050201@monstr.eu>

On Mon, Jun 08, 2015 at 10:06:30AM +0200, Michal Simek wrote:
> On 06/05/2015 05:11 PM, Bjorn Helgaas wrote:
> > On Fri, Jun 5, 2015 at 2:07 AM, Michal Simek <monstr@monstr.eu> wrote:
> >> On 06/04/2015 11:49 PM, Bjorn Helgaas wrote:
> >>> The following declarations were copied from powerpc but are unused on
> >>> microblaze:
> >>>
> >>>   struct pci_controller *init_phb_dynamic(struct device_node *dn)
> >>>   int remove_phb_dynamic(struct pci_controller *phb)
> >>>   struct pci_dev *of_create_pci_dev(struct device_node *node, ...)
> >>>   void of_scan_pci_bridge(struct device_node *node, ...)
> >>>   void of_scan_bus(struct device_node *node, struct pci_bus *bus)
> >>>   void of_rescan_bus(struct device_node *node, struct pci_bus *bus)
> >>>
> >>> Remove them.
> >>>
> >>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> >>> CC: Michal Simek <monstr@monstr.eu>
> >>> ---
> >>>  arch/microblaze/include/asm/pci.h |   12 ------------
> >>>  1 file changed, 12 deletions(-)
> >>
> >> Reviewed-by: Michal Simek <michal.simek@xilinx.com>
> >>
> >> Bjorn: Do you want me to take this via Microblaze tree?
> > 
> > Sure, it'd be great if you take all the Microblaze-specific patches.
> > There aren't any dependencies on them, so there shouldn't be any
> > problem.
> 
> Ok. Added these 3 patches to microblaze next branch - it will be in
> linux-next tmr.

Great, thanks!  I dropped them from my branch.

> > I do have a Microblaze hunk in "PCI: Remove unused
> > pci_dma_burst_advice()" and if you agree, I'll merge that one through
> > my tree since the change for each arch is essentially identical.
> 
> No problem at all. Feel free to add there my acked-by line for microblaze.

Done, thanks again!

Bjorn

  reply	other threads:[~2015-06-08 12:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 21:49 [PATCH 0/7] Cleanup unused code Bjorn Helgaas
2015-06-04 21:49 ` [PATCH 1/7] microblaze/PCI: Remove unused declarations Bjorn Helgaas
2015-06-05  7:07   ` Michal Simek
2015-06-05 15:11     ` Bjorn Helgaas
2015-06-08  8:06       ` Michal Simek
2015-06-08 12:58         ` Bjorn Helgaas [this message]
2015-06-04 21:49 ` [PATCH 2/7] microblaze/PCI: Remove unnecessary pci_bus_find_capability() declaration Bjorn Helgaas
2015-06-05  7:07   ` Michal Simek
2015-06-04 21:49 ` [PATCH 3/7] microblaze/PCI: Remove unnecessary struct pci_dev declaration Bjorn Helgaas
2015-06-05  7:07   ` Michal Simek
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
2015-06-04 21:50 ` [PATCH 6/7] PCI: Remove unused pcibios_select_root() (again) Bjorn Helgaas
2015-06-04 21:50 ` [PATCH 7/7] PCI: Remove unused pci_dma_burst_advice() Bjorn Helgaas

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=20150608125846.GV3631@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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).