From: Michal Simek <michal.simek@xilinx.com>
To: Borislav Petkov <bp@alien8.de>, Michal Simek <michal.simek@xilinx.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
leoyang.li@nxp.com, robh+dt@kernel.org,
Manish Narani <manish.narani@xilinx.com>,
sudeep.holla@arm.com, Olof Johansson <olof@lixom.net>,
mchehab@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-edac@vger.kernel.org
Subject: Re: [PATCH v10 5/6] arm64: zynqmp: Add DDRC node
Date: Mon, 5 Nov 2018 14:32:55 +0100 [thread overview]
Message-ID: <a81f47e0-1778-a6ac-4cd8-634502661d6f@xilinx.com> (raw)
In-Reply-To: <20181105132007.GB7937@zn.tnic>
On 05. 11. 18 14:20, Borislav Petkov wrote:
> On Mon, Nov 05, 2018 at 02:06:11PM +0100, Michal Simek wrote:
>> I don't think that driver will be broken. You can build them, use them
>> on out of tree HW. And when this patch is merged to mainline it will be
>> enabled for xilinx soc.
>
> But if the DT entries are missing, the driver won't load, would it?
you don't have that HW anyway.
>
>> TBH I can't see any reason to do merges but if you want to do that way
>> we can also do it.
>
> The reason is because there's a separate DT tree and all those arm
> drivers need DT.
>
> I have already acked EDAC patches to go through other trees too, FWIW.
I looked at v10 and I can't see your ack there. Can you please give me a
link?
I see Rob's reviewed by in v10 2/6
> Which is not optimal either if someone sends fixes ontop but I cannot
> apply them yet because the dependent patches are in a different tree.
>
> So yes, there are at least two good reasons for merging a shared branch.
I have not a problem with that. I can simply take patch (process via
arm-soc) with pointing to reviewed binding doc and you will take the
rest when this is in arm-soc tree.
Thanks,
Michal
next prev parent reply other threads:[~2018-11-05 13:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 6:06 [PATCH v10 0/6] EDAC: Enhancements to Synopsys EDAC driver Manish Narani
2018-10-25 6:06 ` [PATCH v10 1/6] edac: synopsys: Add error handling for NULL in probe() Manish Narani
2018-10-25 6:06 ` [PATCH v10 2/6] dt: bindings: Document ZynqMP DDRC in Synopsys documentation Manish Narani
2018-10-25 6:06 ` [PATCH v10 3/6] edac: synopsys: Add macro defines for ZynqMP DDRC Manish Narani
2018-10-25 6:06 ` [PATCH v10 4/6] edac: synopsys: Add EDAC ECC support " Manish Narani
2018-10-25 6:07 ` [PATCH v10 5/6] arm64: zynqmp: Add DDRC node Manish Narani
2018-11-05 12:56 ` Borislav Petkov
2018-11-05 13:06 ` Michal Simek
2018-11-05 13:20 ` Borislav Petkov
2018-11-05 13:32 ` Michal Simek [this message]
2018-11-05 13:42 ` Borislav Petkov
2018-11-05 13:45 ` Michal Simek
2018-11-05 14:51 ` Olof Johansson
2018-11-05 19:47 ` Borislav Petkov
2018-11-05 20:38 ` Olof Johansson
2018-11-05 20:43 ` Borislav Petkov
2018-11-06 6:46 ` Michal Simek
2018-11-06 9:22 ` Borislav Petkov
2018-11-06 11:54 ` Michal Simek
2018-10-25 6:07 ` [PATCH v10 6/6] edac: synopsys: Add Error Injection support for ZynqMP DDRC Manish Narani
2018-11-02 8:38 ` [PATCH v10 0/6] EDAC: Enhancements to Synopsys EDAC driver Manish Narani
2018-11-02 8:58 ` Borislav Petkov
2018-11-06 10:03 ` Borislav Petkov
2018-11-06 10:42 ` Manish Narani
2018-11-06 10:58 ` 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=a81f47e0-1778-a6ac-4cd8-634502661d6f@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=amit.kucheria@linaro.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).