From: Thor Thayer <thor.thayer@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: dinguyen@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
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 17:32:07 -0500 [thread overview]
Message-ID: <f843024e-5f06-a566-7ab4-5c3e03e6ed3f@linux.intel.com> (raw)
In-Reply-To: <20190409201323.GD6150@zn.tnic>
Hi Boris,
On 4/9/19 3:13 PM, Borislav Petkov wrote:
> On Tue, Apr 09, 2019 at 02:11:58PM -0500, Thor Thayer wrote:
>> If possible, I'd like this series to go through the EDAC tree since future
>> patches will follow this format.
>
> You know how that works - I need ACKs.
>
I have ACKs on patches 1 & 3. Patch 2 has a Reviewed-by from Rob Herring
which was sufficient in the past.
Here are the links to the original ACKs and Reviewed-by.
Patch 1: https://patchwork.codeaurora.org/patch/737155/
Patch 2: https://patchwork.codeaurora.org/patch/757205/
Patch 3: https://patchwork.codeaurora.org/patch/757207/
next prev parent reply other threads:[~2019-04-09 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 14:36 [RESEND PATCHv3 0/3] Update Stratix10 EDAC Bindings thor.thayer
2019-04-04 14:36 ` [RESEND PATCHv3 1/3] Documentation: dt: edac: Fix Stratix10 IRQ bindings thor.thayer
2019-04-04 14:36 ` [RESEND PATCHv3 2/3] Documentation: dt: edac: Add Stratix10 Peripheral bindings thor.thayer
2019-04-04 14:36 ` [RESEND PATCHv3 3/3] arm64: dts: stratix10: Use new Stratix10 EDAC bindings thor.thayer
2019-04-09 19:11 ` [RESEND PATCHv3 0/3] Update Stratix10 EDAC Bindings Thor Thayer
2019-04-09 20:13 ` Borislav Petkov
2019-04-09 22:32 ` Thor Thayer [this message]
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=f843024e-5f06-a566-7ab4-5c3e03e6ed3f@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;
as well as URLs for NNTP newsgroup(s).