linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU
Date: Tue, 30 May 2017 16:08:01 +0100	[thread overview]
Message-ID: <20170530150801.GV22219@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170530144934.GB22758@lunn.ch>

On Tue, May 30, 2017 at 04:49:34PM +0200, Andrew Lunn wrote:
> On Tue, May 30, 2017 at 03:39:02PM +0100, Russell King - ARM Linux wrote:
> > On Tue, May 30, 2017 at 03:27:35PM +0200, Andrew Lunn wrote:
> > > What might help is that you ask for help getting them merged. I know
> > > of at least 4 groups of people interested in your devlink and 10G PHY
> > > code. If you handed those patches over to these people, i'm sure we
> > > could find somebody to post them to the list, deal with the feedback,
> > > etc, to get them merged. It just needs you to say it is O.K. for
> > > somebody to take patches from your git tree.
> > 
> > Is that not what I'm trying to do with these A8k changes?  What I'm
> > instead getting is "your tree is private, we're not touching it".
> > 
> > Okay, so let me put it another way: please help me merge the A8k
> > changes that I have in my tree.
> 
> Hi Russell
> 
> So you are happy for Free-Electrons, or anybody else, to take patches
> from your tree, submit them, handle comments, resubmit them, etc?

I am happy for the A8k changes, provided there's coordination, so we
reasonably avoid to duplicate effort, but I think we're already at
the point where most of my effort has already been duplicated.

If someone wants to take (eg) my ICU patches and fit what's appropriate
on top of Thomas', then I'd welcome that effort.

Obviously, the PP2x changes in my tree are no-hopers for mainline as
the decision has been made to improve the existing PP2 driver, and
I think the gpio/pinctrl changes are now no-hopers as that work has
already been done independently.

I'm not sure there's much other stuff left out of the 63 patches that
comprise my "mvebu" branch as far as core A8k changes go.

For the mcbin changes (that come after the mvebu/phy merge), I think
everything up to and including "arm64: dts: marvell: mcbin: add GPIO"
is probably mainline-candidates (except for the PP2 driver obviously),
the sdhci DTS patch has already been picked up.

"arm64: dts: marvell: mcbin: workaround wrongly wired i2c1 bus" is
definitely not for mainline, as that is only for early revision
boards, and SR does not want that merged into mainline (as stated
in its commit log.)

"arm64: dts: marvell: mcbin: add remainder of pinctrls" and
"usb: host: xhci: mvebu: add reset on resume quirk" might also be
candidates, I'm not sure without looking further.

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

  reply	other threads:[~2017-05-30 15:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  9:16 [PATCH 0/6] Add support for the ICU unit in Marvell Armada 7K/8K Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 1/6] dt-bindings: interrupt-controller: add DT binding for the Marvell GICP Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 2/6] dt-bindings: interrupt-controller: add DT binding for the Marvell ICU Thomas Petazzoni
2017-05-30 10:37   ` Marc Zyngier
2017-05-30 11:41     ` Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP Thomas Petazzoni
2017-05-30 13:55   ` Marc Zyngier
2017-05-30 14:54     ` Thomas Petazzoni
2017-05-30 15:17       ` Marc Zyngier
2017-05-30 15:25         ` Thomas Petazzoni
2017-05-30 15:33           ` Marc Zyngier
2017-05-30  9:16 ` [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU Thomas Petazzoni
2017-05-30 11:10   ` Marc Zyngier
2017-05-30 12:05     ` Thomas Petazzoni
2017-05-30 13:06       ` Marc Zyngier
2017-05-30 13:17         ` Thomas Petazzoni
2017-05-30 13:40           ` Marc Zyngier
2017-06-25  6:47       ` [EXT] " Yehuda Yitschak
2017-05-30 12:04   ` Antoine Tenart
2017-05-30 12:19   ` Russell King - ARM Linux
2017-05-30 12:33     ` Thomas Petazzoni
2017-05-30 12:56       ` Russell King - ARM Linux
2017-05-30 13:27         ` Andrew Lunn
2017-05-30 13:34           ` Thomas Petazzoni
2017-05-30 13:42           ` Russell King - ARM Linux
2017-05-30 14:03             ` Andrew Lunn
2017-05-30 14:36               ` Russell King - ARM Linux
2017-05-30 14:26             ` Thomas Petazzoni
2017-05-30 14:39           ` Russell King - ARM Linux
2017-05-30 14:49             ` Andrew Lunn
2017-05-30 15:08               ` Russell King - ARM Linux [this message]
2017-05-30 13:28         ` Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 5/6] arm64: marvell: enable ICU and GICP drivers Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 6/6] arm64: dts: marvell: enable GICP and ICU on Armada 7K/8K Thomas Petazzoni
2017-05-30 14:02   ` Marc Zyngier
2017-05-30 14:28     ` Thomas Petazzoni
2017-05-30  9:16 ` [PATCH 6/6] arm64: dts: marvell: enable GICP and ICU Thomas Petazzoni
2017-05-30  9:22   ` Thomas Petazzoni
2017-05-30 14:15 ` [PATCH 0/6] Add support for the ICU unit in Marvell Armada 7K/8K Marc Zyngier

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=20170530150801.GV22219@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;
as well as URLs for NNTP newsgroup(s).