From: Borislav Petkov <bp@alien8.de>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Manish Narani <manish.narani@xilinx.com>,
robh+dt@kernel.org, mark.rutland@arm.com, mchehab@kernel.org,
amit.kucheria@linaro.org, sudeep.holla@arm.com,
leoyang.li@nxp.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: [v10,5/6] arm64: zynqmp: Add DDRC node
Date: Mon, 5 Nov 2018 14:20:07 +0100 [thread overview]
Message-ID: <20181105132007.GB7937@zn.tnic> (raw)
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?
> 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.
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.
next reply other threads:[~2018-11-05 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 13:20 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-06 11:54 [v10,5/6] arm64: zynqmp: Add DDRC node Michal Simek
2018-11-06 9:22 Borislav Petkov
2018-11-06 6:46 Michal Simek
2018-11-05 20:43 Borislav Petkov
2018-11-05 20:38 Olof Johansson
2018-11-05 19:47 Borislav Petkov
2018-11-05 14:51 Olof Johansson
2018-11-05 13:45 Michal Simek
2018-11-05 13:42 Borislav Petkov
2018-11-05 13:32 Michal Simek
2018-11-05 13:06 Michal Simek
2018-11-05 12:56 Borislav Petkov
2018-10-25 6:07 Manish Narani
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=20181105132007.GB7937@zn.tnic \
--to=bp@alien8.de \
--cc=amit.kucheria@linaro.org \
--cc=arnd@arndb.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=michal.simek@xilinx.com \
--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