All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: marvell: mcbin: Enable PCIe interface
Date: Thu, 06 Jul 2017 13:38:30 +0200	[thread overview]
Message-ID: <87van5eqx5.fsf@free-electrons.com> (raw)
In-Reply-To: <20170706090143.GI4902@n2100.armlinux.org.uk> (Russell King's message of "Thu, 6 Jul 2017 10:01:43 +0100")

Hi Russell King,
 
 On jeu., juil. 06 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:

> 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

Well for upstreaming I don't see the problem to base on a linux-net tags
such as next-20170704. We do it often when we submit patches to various
subsystem (and if it is not a next tag we merge various branch by
ourselves).

> changes on and publish back to SolidRun for their use, that would be
> insane.

We also deliver stable branch for various customers and in this case we
just have a different branch or tree.

However, I think we have exactly what meets your requirements:
https://github.com/MISL-EBU-System-SW/mainline-public/tree/4.12-rc6/backports

It is a stable branch which gathers most of the patch submitted for
Armada 37xx, 7K and 8K.

Gregory

>
> -- 
> 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.

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2017-07-06 11:38 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
2017-07-06 11:38       ` Gregory CLEMENT [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=87van5eqx5.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --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 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.