From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org,
Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
devicetree@vger.kernel.org, tony.luck@intel.com,
mchehab@kernel.org, michal.simek@xilinx.com, git@amd.com,
robh+dt@kernel.org, james.morse@arm.com, rric@kernel.org
Subject: Re: (subset) [PATCH v2 1/2] dt-bindings: edac: Add bindings for Xilinx Versal EDAC for DDRMC
Date: Thu, 10 Nov 2022 11:57:11 +0100 [thread overview]
Message-ID: <490d26ce-a09c-db16-93b1-8f468a5c3f87@linaro.org> (raw)
In-Reply-To: <Y2zYqetP6IhG01Bg@zn.tnic>
On 10/11/2022 11:55, Borislav Petkov wrote:
> On Thu, Nov 10, 2022 at 11:03:43AM +0100, Krzysztof Kozlowski wrote:
>> Unless you mean some EDAC-tree Patchwork tests, what's in the next
>> matters. Both patches will be in next, so no warnings.
>
> Yeah, that is correct.
>
>> If you take it, then all other patches touching these files in this
>> cycle must go via your tree.
>
> Do you expect that happening this cycle?
>
> If so, then we can do them this way and I'll ignore those warnings.
>
>> Sure, I'll provide feedback and drop the patches.
>
> Right, in the past devicetree and driver patches for EDAC drivers have
> gone together through my tree but if you anticipate conflicts then sure,
> let's split them.
I don't anticipate more work for current cycle... but I also did not
anticipate such in other occasions (e.g. recently Tegra binding
headers), so my anticipation is not accurate. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-10 10:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 6:24 [PATCH v2 0/2] edac: xilinx: Added EDAC support for Xilinx DDR controller Shubhrajyoti Datta
2022-11-07 6:24 ` [PATCH v2 1/2] dt-bindings: edac: Add bindings for Xilinx Versal EDAC for DDRMC Shubhrajyoti Datta
2022-11-10 9:10 ` (subset) " Krzysztof Kozlowski
2022-11-10 10:01 ` Borislav Petkov
2022-11-10 10:03 ` Krzysztof Kozlowski
2022-11-10 10:55 ` Borislav Petkov
2022-11-10 10:57 ` Krzysztof Kozlowski [this message]
2022-11-10 10:59 ` Borislav Petkov
2022-11-10 11:00 ` Krzysztof Kozlowski
2022-11-10 11:07 ` Borislav Petkov
2022-11-10 9:11 ` Krzysztof Kozlowski
2022-11-10 10:05 ` Krzysztof Kozlowski
2022-11-07 6:24 ` [PATCH v2 2/2] edac: xilinx: Added EDAC support for Xilinx DDR controller Shubhrajyoti Datta
2022-11-08 19:07 ` [PATCH v2 0/2] " Borislav Petkov
2022-11-09 12:43 ` Datta, Shubhrajyoti
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=490d26ce-a09c-db16-93b1-8f468a5c3f87@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=shubhrajyoti.datta@amd.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox