From: Boris Petkov <bp@alien8.de>
To: James Morse <james.morse@arm.com>
Cc: Yash Shah <yash.shah@sifive.com>,
linux-edac@vger.kernel.org, linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-kernel@vger.kernel.org, aou@eecs.berkeley.edu,
mchehab@kernel.org, Sachin Ghadi <sachin.ghadi@sifive.com>,
davem@davemloft.net, gregkh@linuxfoundation.org,
nicolas.ferre@microchip.com, paulmck@linux.ibm.com
Subject: Re: [PATCH v2] edac: sifive: Add EDAC platform driver for SiFive SoCs
Date: Wed, 22 May 2019 04:34:38 -0500 [thread overview]
Message-ID: <ABA6726C-CC1D-4092-887E-7D5A5B90509B@alien8.de> (raw)
In-Reply-To: <1c7eb8ab-6f48-c41a-1d3a-a9b0f5ce8a7f@arm.com>
On May 22, 2019 4:13:59 AM CDT, James Morse <james.morse@arm.com> wrote:
>Hi Boris,
>
>On 21/05/2019 19:21, Borislav Petkov wrote:
>> On Tue, May 21, 2019 at 11:00:59AM +0530, Yash Shah wrote:
>>> The prerequisite patch (sifive_l2_cache driver) has been merged into
>>> mainline v5.2-rc1
>>> It should be OK to merge this edac driver now.
>>
>> James?
>
>Still fine by me:
>Reviewed-by: James Morse <james.morse@arm.com>
>
>(...this patch already has my reviewed-by on it...)
>
>I commented that it couldn't be merged in pieces here:
>https://lore.kernel.org/lkml/4072c812-d3bf-9ad5-2b30-6b2a5060bb55@arm.com/T/#u
>
>which is what Yash is replying to.
Ok, I'll take it when I get back. Thanks for clarifying.
--
Sent from a small device: formatting sux and brevity is inevitable.
WARNING: multiple messages have this Message-ID (diff)
From: Boris Petkov <bp@alien8.de>
To: James Morse <james.morse@arm.com>
Cc: aou@eecs.berkeley.edu, paulmck@linux.ibm.com,
gregkh@linuxfoundation.org, Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, nicolas.ferre@microchip.com,
Sachin Ghadi <sachin.ghadi@sifive.com>,
Yash Shah <yash.shah@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, mchehab@kernel.org,
davem@davemloft.net, linux-edac@vger.kernel.org
Subject: Re: [PATCH v2] edac: sifive: Add EDAC platform driver for SiFive SoCs
Date: Wed, 22 May 2019 04:34:38 -0500 [thread overview]
Message-ID: <ABA6726C-CC1D-4092-887E-7D5A5B90509B@alien8.de> (raw)
In-Reply-To: <1c7eb8ab-6f48-c41a-1d3a-a9b0f5ce8a7f@arm.com>
On May 22, 2019 4:13:59 AM CDT, James Morse <james.morse@arm.com> wrote:
>Hi Boris,
>
>On 21/05/2019 19:21, Borislav Petkov wrote:
>> On Tue, May 21, 2019 at 11:00:59AM +0530, Yash Shah wrote:
>>> The prerequisite patch (sifive_l2_cache driver) has been merged into
>>> mainline v5.2-rc1
>>> It should be OK to merge this edac driver now.
>>
>> James?
>
>Still fine by me:
>Reviewed-by: James Morse <james.morse@arm.com>
>
>(...this patch already has my reviewed-by on it...)
>
>I commented that it couldn't be merged in pieces here:
>https://lore.kernel.org/lkml/4072c812-d3bf-9ad5-2b30-6b2a5060bb55@arm.com/T/#u
>
>which is what Yash is replying to.
Ok, I'll take it when I get back. Thanks for clarifying.
--
Sent from a small device: formatting sux and brevity is inevitable.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-22 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 11:27 [PATCH v2] EDAC support for SiFive SoCs Yash Shah
2019-05-06 11:27 ` Yash Shah
2019-05-06 11:27 ` [PATCH v2] edac: sifive: Add EDAC platform driver " Yash Shah
2019-05-06 11:27 ` Yash Shah
2019-05-21 5:30 ` Yash Shah
2019-05-21 5:30 ` Yash Shah
2019-05-21 18:21 ` Borislav Petkov
2019-05-21 18:21 ` Borislav Petkov
2019-05-22 9:13 ` James Morse
2019-05-22 9:13 ` James Morse
2019-05-22 9:34 ` Boris Petkov [this message]
2019-05-22 9:34 ` Boris Petkov
2019-06-07 6:43 ` Borislav Petkov
2019-06-07 6:43 ` 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=ABA6726C-CC1D-4092-887E-7D5A5B90509B@alien8.de \
--to=bp@alien8.de \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@linux.ibm.com \
--cc=sachin.ghadi@sifive.com \
--cc=yash.shah@sifive.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.