From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: "james.morse@arm.com" <james.morse@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"jlu@pengutronix.de" <jlu@pengutronix.de>,
"bp@alien8.de" <bp@alien8.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"patches@armlinux.org.uk" <patches@armlinux.org.uk>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH v9 0/8] EDAC drivers for Armada XP L2 and DDR
Date: Sun, 28 Jul 2019 20:33:03 +0000 [thread overview]
Message-ID: <1564345983.9737.9.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <d1dfe8ec-66e8-e2c8-5421-a18d7e7fc8fc@arm.com>
On Fri, 2019-07-26 at 15:53 +0100, James Morse wrote:
> Hi Chris,
>
> On 12/07/2019 04:48, Chris Packham wrote:
> >
> > I still seem to be struggling to get this on anyone's radar.
> Whose radar does it need to cross?
>
That's a good question. The last solid guidance I had was that this
series was going in via the ARM tree. But as you say below that was two
years ago.
I only realised recently that the ARM core seems to have a different
workflow to other kernel subsystems.
>
> >
> > The Reviews/Acks have been given so this should be good to go in
> > via the ARM
> > tree as planned.
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-August/5
> > 25561.html
> For your v8 I took this to mean this series was done!
>
> If nothing has changed with Boris and Russell's decision (it was two
> years ago....),
> details of the patch system are here:
>
> https://lore.kernel.org/linux-arm-kernel/20190624142346.pxljv3m4npatd
> iyk@shell.armlinux.org.uk/
>
Thanks for the link. I would have never found that. I did try to follow
what I could find on https://www.armlinux.org.uk/developer/ but a lot
of that seems to be out of date.
I did manage to submit v9 to the ARM patch tracker but naturally I
messed it up the first time https://www.armlinux.org.uk/developer/patch
es/viewpatch.php?id=8877/1 and I'm not sure I got the second attempt
right either https://www.armlinux.org.uk/developer/patches/viewpatch.ph
p?id=8885/1
> Thanks,
>
> James
prev parent reply other threads:[~2019-07-28 20:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 3:48 [PATCH v9 0/8] EDAC drivers for Armada XP L2 and DDR Chris Packham
2019-07-12 3:48 ` [PATCH v9 1/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Chris Packham
2019-08-23 10:46 ` Russell King - ARM Linux admin
2019-08-23 10:50 ` Russell King - ARM Linux admin
2019-08-26 0:46 ` Chris Packham
2019-08-27 9:13 ` Russell King - ARM Linux admin
2019-08-27 20:56 ` Chris Packham
2019-08-27 21:07 ` Russell King - ARM Linux admin
2019-08-27 21:13 ` Chris Packham
2019-08-27 21:15 ` Russell King - ARM Linux admin
2019-07-12 3:48 ` [PATCH v9 2/8] ARM: aurora-l2: add defines for parity and ECC registers Chris Packham
2019-07-12 3:48 ` [PATCH v9 3/8] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2019-07-12 3:49 ` [PATCH v9 4/8] dt-bindings: ARM: document marvell,ecc-enable binding Chris Packham
2019-07-12 3:49 ` [PATCH v9 5/8] ARM: l2x0: add marvell,ecc-enable property for aurora Chris Packham
2019-07-12 3:49 ` [PATCH v9 6/8] EDAC: Add missing debugfs_create_x32 wrapper Chris Packham
2019-07-12 3:49 ` [PATCH v9 7/8] EDAC: Add driver for the Marvell Armada XP SDRAM and L2 cache ECC Chris Packham
2019-07-12 3:49 ` [PATCH v9 8/8] EDAC: armada_xp: Add support for more SoCs Chris Packham
2019-07-26 14:51 ` James Morse
2019-07-28 20:52 ` Chris Packham
2019-07-26 14:53 ` [PATCH v9 0/8] EDAC drivers for Armada XP L2 and DDR James Morse
2019-07-28 20:33 ` Chris Packham [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=1564345983.9737.9.camel@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=jlu@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=patches@armlinux.org.uk \
--cc=robh+dt@kernel.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).