From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Grant Likely <grant.likely@secretlab.ca>,
Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
linux-pci@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Thierry Reding <thierry.reding@avionic-design.de>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Maen Suleiman <maen@marvell.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Andrew Murray <andrew.murray@arm.com>,
Tawfik Bayouk <tawfik@marvell.com>,
linux-arm-kernel@lists.infradead.org,
Mitch Bradley <wmb@firmworks.com>
Subject: Re: [PATCHv8 07/19] arm: pci: add a align_resource hook
Date: Fri, 19 Apr 2013 15:33:31 +0100 [thread overview]
Message-ID: <20130419143331.GV14496@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130415163609.GJ28693@titan.lakedaemon.net>
On Mon, Apr 15, 2013 at 12:36:09PM -0400, Jason Cooper wrote:
> Russell,
>
> Thanks for applying this patch (7683/1) to your tree. I see it's in
> your for-next, which I understand *isn't* stable.
That is correct.
> 029baf1 ARM: 7683/1: pci: add a align_resource hook
>
> Is there a stable branch I could depend on for the rest of this series
> (particularly, patch 10)? It looks like you applied it to your misc
> branch, but that's not currently available.
I will have to look at that; as I'm still catching up with mail three
days after having returned and there's still quite an amount outstanding,
it's going to be a while before I can look at this. Given that we're at
-rc7 and the amount of outstanding mail, it's likely that may happen
after the merge window has opened.
next prev parent reply other threads:[~2013-04-19 14:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 21:06 [PATCHv8 00/19] PCIe support for the Armada 370 and Armada XP SoCs Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 01/19] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 02/19] of/pci: Provide support for parsing PCI DT ranges property Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 03/19] of/pci: mips: convert to common of_pci_range_parser Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 04/19] of/pci: Add of_pci_get_devfn() function Thomas Petazzoni
2013-04-10 18:33 ` Rob Herring
2013-04-09 21:06 ` [PATCHv8 05/19] of/pci: Add of_pci_parse_bus_range() function Thomas Petazzoni
2013-04-10 18:37 ` Rob Herring
2013-04-09 21:06 ` [PATCHv8 06/19] pci: infrastructure to add drivers in drivers/pci/host Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 07/19] arm: pci: add a align_resource hook Thomas Petazzoni
2013-04-15 16:36 ` Jason Cooper
[not found] ` <20130415163609.GJ28693-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-04-17 14:08 ` Jason Cooper
2013-04-19 14:33 ` Russell King - ARM Linux [this message]
2013-04-09 21:06 ` [PATCHv8 08/19] clk: mvebu: create parent-child relation for PCIe clocks on Armada 370 Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 09/19] clk: mvebu: add more PCIe clocks for Armada XP Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 10/19] pci: PCIe driver for Marvell Armada 370/XP systems Thomas Petazzoni
2013-04-09 21:12 ` Bjorn Helgaas
2013-04-09 21:22 ` Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 11/19] arm: mvebu: PCIe support is now available on mvebu Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 12/19] arm: mvebu: add PCIe Device Tree informations for Armada 370 Thomas Petazzoni
2013-04-12 0:28 ` Jason Cooper
[not found] ` <20130412002811.GS28693-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-04-12 0:48 ` Jason Cooper
2013-04-09 21:06 ` [PATCHv8 13/19] arm: mvebu: add PCIe Device Tree informations for Armada XP Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 14/19] arm: mvebu: PCIe Device Tree informations for OpenBlocks AX3-4 Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 15/19] arm: mvebu: PCIe Device Tree informations for Armada XP DB Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 16/19] arm: mvebu: PCIe Device Tree informations for Armada 370 Mirabox Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 17/19] arm: mvebu: PCIe Device Tree informations for Armada 370 DB Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 18/19] arm: mvebu: PCIe Device Tree informations for Armada XP GP Thomas Petazzoni
2013-04-09 21:06 ` [PATCHv8 19/19] arm: mvebu: update defconfig with PCI and USB support Thomas Petazzoni
2013-04-15 15:46 ` [PATCHv8 00/19] PCIe support for the Armada 370 and Armada XP SoCs Jason Cooper
2013-04-15 16:36 ` Thomas Petazzoni
2013-04-15 16:38 ` Jason Cooper
2013-04-15 16:40 ` Thomas Petazzoni
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=20130419143331.GV14496@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alior@marvell.com \
--cc=andrew.murray@arm.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=maen@marvell.com \
--cc=olof@lixom.net \
--cc=tawfik@marvell.com \
--cc=thierry.reding@avionic-design.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wmb@firmworks.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 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).