From: Olof Johansson <email@example.com>
To: Borislav Petkov <firstname.lastname@example.org>
Cc: Michal Simek <email@example.com>,
Arnd Bergmann <firstname.lastname@example.org>,
email@example.com, Rob Herring <firstname.lastname@example.org>,
Mark Rutland <email@example.com>,
Mauro Carvalho Chehab <firstname.lastname@example.org>,
Amit Kucheria <email@example.com>,
Sudeep Holla <firstname.lastname@example.org>, Li Yang <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Linux ARM Mailing List <email@example.com>,
Subject: Re: [PATCH v10 5/6] arm64: zynqmp: Add DDRC node
Date: Mon, 5 Nov 2018 12:38:05 -0800 [thread overview]
Message-ID: <CAOesGMjsPWeRZEeBH37uLQFBKwAWNMh5yCvuKNYrOUDfRSSYog@mail.gmail.com> (raw)
On Mon, Nov 5, 2018 at 11:47 AM Borislav Petkov <firstname.lastname@example.org> wrote:
> Hi Olof,
> On Mon, Nov 05, 2018 at 06:51:26AM -0800, Olof Johansson wrote:
> > In general, for new functionality where needing both the driver change
> > and a DT change to enable it (or a driver change and a config change
> > to enable it), we have been merging the changes separately between
> > driver trees and arm-soc. I.e. things will be in place, but not
> > enabled, until both sides land. Main reason for doing so is to cut
> > down on arbitrary dependencies between the trees, since there can
> > sometimes end up being a lot of them.
> Well, makes sense too and it is the least problematic approach. :-)
> > Since DT should strive for being backwards compatible (i.e, a driver
> > change shouldn't require a DT change for the kernel to not regress
> > functionally), this has been working pretty well.
> > However, if there's some other reason to share a base between the two
> > trees, we can do that. For most cases we've found that it's not needed
> > though. So let us know what you prefer here.
> No, I just wanted to make sure drivers can still function when they go
> to linux-next. But I certainly can get on board with keeping drivers and
> DT changes separate as it requires no sync and the short period of time
> when they don't load in linux-next, is perfectly ok.
Ok, sounds good.
> So can I assume you guys are going to pick up:
Yeah, Michal should pick those up for his platform and send them in to
us (or let us know if he wants us to take them directly, but usually
they come in through platform maintainers sending us pull requests).
> I can then pick up the rest.
> And I'll be ignoring DT stuff sent to me from now on and concentrate on
> the EDAC drivers, assuming former will go through your tree.
> Sounds good?
Yeah, that's the way we've been trying to do for various subsystems
and it's been working pretty well. Of course, if there's need to
coordinate more closely for something in the future we'll be happy to
next prev parent reply other threads:[~2018-11-05 20:38 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
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 [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).