From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/8] EDAC drivers for Armada XP L2 and DDR
Date: Tue, 9 Oct 2018 09:06:12 +0200 [thread overview]
Message-ID: <20181009070612.f3zrygvoj2xoeook@pengutronix.de> (raw)
In-Reply-To: <2688131645a34eeda96894e154bba8d0@svr-chch-ex1.atlnz.lc>
Hello Chris,
On Thu, May 03, 2018 at 08:54:36PM +0000, Chris Packham wrote:
> On 03/05/18 21:22, Jan L?bbe wrote:
> > On Fri, 2018-01-12 at 14:27 +1300, Chris Packham wrote:
> >> I've found some time to address Borislav's comments (I think I've got them
> >> all). The patches affected are 3/8 and 7/8. The changes are all reasonably
> >> cosmetic and I can confirm with the addition of 8/8 that the (mc) EDAC
> >> reporting works on Armada-38x.
> >>
> >> The current plan is for these to go in via the ARM tree once appropriate
> >> Reviews/Acks have been given.
> >
> > I've finally found some time to look at this again. :)
> >
> > As far as I can see, Borislav has reviewed the edac bits and Rob has
> > review the binding for marvell,ecc-enable. I'm not sure where it got
> > stuck though. Russell wanted to merge the whole series? Or am i missing
> > something?
> >
>
> Yes I was expecting it to come in via the ARM tree. It may have got lost
> in the noise of the merge window. I checked a few times but I didn't
> want to add to the noise.
>
> Given that it's been a while: ping.
During an internal review of some patches in a BSP I stumbled over this
series.
I noticed that some patches (at least 1 and 2) don't have your S-o-b.
Patch 4 doesn't have it as last entry.
Didn't look in more detail, but maybe fix this formalism (which for sure
will prevent application of this series) and resend on top of a recent
tree?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2018-10-09 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180112012755.20495-1-chris.packham@alliedtelesis.co.nz>
2018-01-12 1:27 ` [PATCH v4 1/8] ARM: l2c: move cache-aurora-l2.h to asm/hardware Chris Packham
2018-01-12 1:27 ` [PATCH v4 2/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE Chris Packham
2018-01-12 1:27 ` [PATCH v4 3/8] ARM: aurora-l2: add defines for parity and ECC registers Chris Packham
2018-01-12 1:27 ` [PATCH v4 4/8] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2018-01-12 1:27 ` [PATCH v4 5/8] ARM: l2x0: add marvell,ecc-enable property for aurora Chris Packham
2018-01-19 21:28 ` Rob Herring
[not found] ` <1525338355.17782.21.camel@pengutronix.de>
2018-05-03 20:54 ` [PATCH v4 0/8] EDAC drivers for Armada XP L2 and DDR Chris Packham
2018-10-09 7:06 ` Uwe Kleine-König [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=20181009070612.f3zrygvoj2xoeook@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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