From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Marcin Wojtas" <mw@semihalf.com>, "Andrew Lunn" <andrew@lunn.ch>,
"Jason Cooper" <jason@lakedaemon.net>,
"jaz@semihalf.com" <jaz@semihalf.com>,
"Will Deacon" <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, nadavh@marvell.com,
"Rob Herring" <robh+dt@kernel.org>,
"Neta Zur Hershkovits" <neta@marvell.com>,
"Tomasz Nowicki" <tn@semihalf.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 1/2] arm64: marvell: dts: fill MachiatoBin board description
Date: Tue, 16 May 2017 11:02:37 +0100 [thread overview]
Message-ID: <20170516100236.GA22219@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170516115535.2faf86ec@free-electrons.com>
On Tue, May 16, 2017 at 11:55:35AM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 16 May 2017 10:50:27 +0100, Russell King - ARM Linux wrote:
>
> > I can't see how you can say that when the branch contains support for
> > SDHCI and ethernet. It obviously will collide, since it conflicts with
> > the changes I have.
>
> Correct, but Marcin has submitted patches, and you haven't.
As I said, give me a friggin chance. You know full well that I've been
working on this, working with you and submitting patches.
> > > The board is starting to get really popular and a lot has been happening
> > > around it recently - missing bits like 'chosen' node or the interfaces
> > > is pretty annoying.
> >
> > Given that features like SDHCI and basic ethernet support have only just
> > been merged during the merge window, how about giving those who are
> > supporting the platform some time to organise their trees and get patches
> > out there, rather than cutting across those who have put considerable
> > effort into the platform already, or working with those who have.
>
> I believe if you say that, it's because you don't know how much work
> Marcin is doing behind the scenes on supporting Marvell platforms, and
> not only at the Linux kernel level.
Maybe Marcin doesn't know how much work I'm doing supporting this board?
> > The whole Armada 8k support is all very new, and there's still lots of
> > fundamental bits that are missing - pinmux and gpio are the two biggest
> > ones.
> >
> > I've already put effort into cleaning up the mvebu pinmux code (already
> > merged) so that we can cleanly merge the pinmux support, but both of
> > these are a sticking point with free-electrons - they have a view on
> > how it should be represented in DT which does not fit with the current
> > orion-gpio usage, nor with the "system controller" being in drivers/clk.
>
> Grégory Clement has been working on this, and he has a patch series
> almost ready to submission.
You've seen my patches, because I've sent them to you in the past.
> > The code which I have in my tree is correct for the Armada 8k hardware
> > (which has some weirdness about which gpios on each CP110 appear to the
> > external world - some are used for inter-CP110 communication and must
> > not be exposed) so any additional work should be based on the code in
> > my tree.
>
> No, there is no rule like this in the kernel community. Whatever is in
> your private tree does not matter. Until it gets submitted, it doesn't
> exist, and nobody is forced to base its work on top of your
> unknown/private trees.
It _has_ been submitted - a few months ago - so you're talking rubbish
here. You just need to check your mailbox.
--
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-05-16 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 23:28 [PATCH 0/2] Armada 8040 MachiatoBin and DB improvements Marcin Wojtas
2017-05-15 23:28 ` [PATCH 1/2] arm64: marvell: dts: fill MachiatoBin board description Marcin Wojtas
2017-05-15 23:28 ` Russell King - ARM Linux
2017-05-16 9:27 ` Marcin Wojtas
2017-05-16 9:50 ` Russell King - ARM Linux
2017-05-16 9:55 ` Thomas Petazzoni
2017-05-16 10:02 ` Russell King - ARM Linux [this message]
2017-05-16 11:52 ` Thomas Petazzoni
2017-05-16 12:13 ` Russell King - ARM Linux
2017-05-16 12:44 ` Marcin Wojtas
2017-05-16 13:45 ` Russell King - ARM Linux
2017-05-16 11:16 ` Russell King - ARM Linux
2017-05-16 11:33 ` Marcin Wojtas
2017-05-16 11:14 ` Russell King - ARM Linux
2017-05-16 12:34 ` Thomas Petazzoni
2017-05-16 12:40 ` Russell King - ARM Linux
2017-05-15 23:28 ` [PATCH 2/2] arm64: marvell: dts: add second 1G port on the Armada 8040 DB Marcin Wojtas
2017-05-23 14:24 ` 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=20170516100236.GA22219@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jaz@semihalf.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tn@semihalf.com \
--cc=will.deacon@arm.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