From: Michael Ellerman <mpe@ellerman.id.au>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Borislav Petkov <bp@alien8.de>
Cc: "linux-edac\@vger.kernel.org" <linux-edac@vger.kernel.org>,
"morbidrsa\@gmail.com" <morbidrsa@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"devicetree\@vger.kernel.org" <devicetree@vger.kernel.org>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support
Date: Fri, 03 Feb 2017 16:12:05 +1100 [thread overview]
Message-ID: <874m0bc0yi.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <de8ec9087f214f2fae67b8ea9be92cdc@svr-chch-ex1.atlnz.lc>
Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
> On 03/02/17 12:55, Michael Ellerman wrote:
>> Chris if you want to send a patch to add the compatible string to the
>> l2cache.txt I would merge that, but honestly it doesn't achieve much
>> other than possibly catching a typo in the compatible name.
>
> I think catching a typo might be worthwhile. It's 5 minutes work for me
> to grep/sed through the code to find existing compatible strings and
> update the document. Which might save someone else a lot of time
> debugging only to find out they've transposed some digits in the dts.
>
> I'll whip something up and send it out shortly.
Thanks.
cheers
next prev parent reply other threads:[~2017-02-03 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 23:16 [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support Chris Packham
2017-02-01 23:27 ` Borislav Petkov
2017-02-01 23:46 ` Chris Packham
2017-02-02 17:30 ` Borislav Petkov
2017-02-02 23:55 ` Michael Ellerman
2017-02-03 0:18 ` Chris Packham
2017-02-03 5:12 ` Michael Ellerman [this message]
2017-02-03 9:46 ` Borislav Petkov
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=874m0bc0yi.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=morbidrsa@gmail.com \
--cc=paulus@samba.org \
--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