From: Thor Thayer <thor.thayer@linux.intel.com>
To: bp@alien8.de, dinguyen@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: mchehab@kernel.org, james.morse@arm.com,
devicetree@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCHv3 0/3] Update Stratix10 EDAC Bindings
Date: Tue, 9 Apr 2019 14:11:58 -0500 [thread overview]
Message-ID: <fa5b2837-9cb0-517c-c491-9b5d3ae0a3a5@linux.intel.com> (raw)
In-Reply-To: <1554388597-28019-1-git-send-email-thor.thayer@linux.intel.com>
Hi Boris,
On 4/4/19 9:36 AM, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
>
> This patch series makes the Stratix10 EDAC Bindings
> specific to the Stratix10 ARM64 architecture.
>
> Instead of using the Arria10 (ARM32) EDAC bindings for
> Stratix10 (ARM64), create Stratix10 specific EDAC bindings
> to capture architecture differences between ARM32 and ARM64.
> This requires fixing the previous Stratix10 bindings.
> Also add the peripheral bindings for the Stratix10.
>
> V2: Remove Stratix10 compatible check.
>
> V3: Remove patches not related to EDAC bindings so that
> this patchset is targeted toward the bindings.
> Improve the Stratix10 specific binding description by
> adding in descriptions of ARM64 differences.
>
> Resend: Add Reviewed-by and Acked-by from bindings and
> socfpga device tree maintainers. I'd like this to go
> through the EDAC tree since future patches will have
> a dependency on these bindings and device tree.
>
> Thor Thayer (3):
> Documentation: dt: edac: Fix Stratix10 IRQ bindings
> Documentation: dt: edac: Add Stratix10 Peripheral bindings
> arm64: dts: stratix10: Use new Stratix10 EDAC bindings
>
> .../devicetree/bindings/edac/socfpga-eccmgr.txt | 135 +++++++++++++++++++--
> arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 25 ++--
> 2 files changed, 138 insertions(+), 22 deletions(-)
>
If possible, I'd like this series to go through the EDAC tree since
future patches will follow this format.
Regards,
Thor
next parent reply other threads:[~2019-04-09 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1554388597-28019-1-git-send-email-thor.thayer@linux.intel.com>
2019-04-09 19:11 ` Thor Thayer [this message]
2019-04-09 20:13 ` [RESEND PATCHv3 0/3] Update Stratix10 EDAC Bindings Borislav Petkov
2019-04-09 22:32 ` Thor Thayer
2019-04-10 19:04 ` 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=fa5b2837-9cb0-517c-c491-9b5d3ae0a3a5@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.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