From: Paul Walmsley <paul.walmsley@sifive.com> 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@sifive.com, bp@alien8.de, paul.walmsley@sifive.com, linux-kernel@vger.kernel.org, aou@eecs.berkeley.edu, mchehab@kernel.org, sachin.ghadi@sifive.com, davem@davemloft.net, gregkh@linuxfoundation.org, nicolas.ferre@microchip.com, paulmck@linux.ibm.com Subject: Re: [PATCH] edac: sifive: Add EDAC platform driver for SiFive SoCs Date: Fri, 3 May 2019 12:25:52 -0700 (PDT) [thread overview] Message-ID: <alpine.DEB.2.21.9999.1905031206450.4777@viisi.sifive.com> (raw) In-Reply-To: <4072c812-d3bf-9ad5-2b30-6b2a5060bb55@arm.com> Hi James, On Thu, 2 May 2019, James Morse wrote: > Having an separately posted dependency like this is tricky, as this code can't be > used/tested until the other bits are merged. ... > Looks good to me. I think this patch should go with its two dependencies, I'm not sure why > it got split off... The split was due to my suggestion to Yash, I think. The motivation was to decouple the L2 cache controller driver's journey upstream from the EDAC driver's upstream path. The patches will go up via separate trees, so the idea was to avoid blocking the L2 cache controller driver on the EDAC driver review path. Thanks for your review, - Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <paul.walmsley@sifive.com> To: James Morse <james.morse@arm.com> Cc: aou@eecs.berkeley.edu, paulmck@linux.ibm.com, gregkh@linuxfoundation.org, palmer@sifive.com, linux-kernel@vger.kernel.org, nicolas.ferre@microchip.com, sachin.ghadi@sifive.com, Yash Shah <yash.shah@sifive.com>, bp@alien8.de, paul.walmsley@sifive.com, linux-riscv@lists.infradead.org, mchehab@kernel.org, davem@davemloft.net, linux-edac@vger.kernel.org Subject: Re: [PATCH] edac: sifive: Add EDAC platform driver for SiFive SoCs Date: Fri, 3 May 2019 12:25:52 -0700 (PDT) [thread overview] Message-ID: <alpine.DEB.2.21.9999.1905031206450.4777@viisi.sifive.com> (raw) In-Reply-To: <4072c812-d3bf-9ad5-2b30-6b2a5060bb55@arm.com> Hi James, On Thu, 2 May 2019, James Morse wrote: > Having an separately posted dependency like this is tricky, as this code can't be > used/tested until the other bits are merged. ... > Looks good to me. I think this patch should go with its two dependencies, I'm not sure why > it got split off... The split was due to my suggestion to Yash, I think. The motivation was to decouple the L2 cache controller driver's journey upstream from the EDAC driver's upstream path. The patches will go up via separate trees, so the idea was to avoid blocking the L2 cache controller driver on the EDAC driver review path. Thanks for your review, - Paul _______________________________________________ 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-03 19:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-02 11:16 [PATCH] EDAC support for SiFive SoCs Yash Shah 2019-05-02 11:16 ` Yash Shah 2019-05-02 11:16 ` [PATCH] edac: sifive: Add EDAC platform driver " Yash Shah 2019-05-02 11:16 ` Yash Shah 2019-05-02 16:42 ` James Morse 2019-05-02 16:42 ` James Morse 2019-05-03 19:25 ` Paul Walmsley [this message] 2019-05-03 19:25 ` Paul Walmsley 2019-05-06 9:50 ` Yash Shah 2019-05-06 9:50 ` Yash Shah
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=alpine.DEB.2.21.9999.1905031206450.4777@viisi.sifive.com \ --to=paul.walmsley@sifive.com \ --cc=aou@eecs.berkeley.edu \ --cc=bp@alien8.de \ --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=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: linkBe 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.