From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: marvell: mcbin: Enable PCIe interface
Date: Thu, 6 Jul 2017 10:01:43 +0100 [thread overview]
Message-ID: <20170706090143.GI4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <874luqf2ym.fsf@free-electrons.com>
On Thu, Jul 06, 2017 at 09:18:25AM +0200, Gregory CLEMENT wrote:
> Hi Russell King,
>
> Actually everything is available in the linux-next branch since one or
> two weeks. So you can rebase and send your series right now.
As there are multiple trees, just specifying a branch is not helpful.
The Xenon SDHCI and ethernet changes were being published through the
MISL tree, but that tree has no for-next branch.
There is no git tree specified in MAINTAINERS either.
So, sorry, I've no idea which tree you're referring to.
And no, I do _not_ want to grab a copy of linux-next to rebase my
changes on and publish back to SolidRun for their use, that would be
insane.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-07-06 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:13 [PATCH] arm64: dts: marvell: mcbin: Enable PCIe interface Gregory CLEMENT
2017-07-05 17:16 ` Russell King - ARM Linux
2017-07-05 17:36 ` Ard Biesheuvel
2017-07-05 17:44 ` Russell King - ARM Linux
2017-07-06 6:31 ` Jisheng Zhang
2017-07-06 8:39 ` Ard Biesheuvel
2017-07-06 12:10 ` Gregory CLEMENT
2017-07-06 12:41 ` Ard Biesheuvel
2017-07-06 12:55 ` Gregory CLEMENT
2017-07-06 13:10 ` Ard Biesheuvel
2017-07-06 7:18 ` Gregory CLEMENT
2017-07-06 9:01 ` Russell King - ARM Linux [this message]
2017-07-06 11:38 ` Gregory CLEMENT
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=20170706090143.GI4902@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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