On Fri, Jun 30, 2023 at 08:17:51AM +0100, Lee Jones wrote: > On Thu, 29 Jun 2023, Mark Brown wrote: > > My suggestion is that once the core is ready to apply that and also > > start applying everything else to Lee's tree as it's ready. A branch > > also works and might come in handy anyway in the case where there's some > > subsystem wide updates in some other subsystem (since it avoids having > > to pull the whole MFD tree in or anything like that) but it's not > > essential to the idea. > The issue we currently have is that the core usually comes with a header > file which is included by some or all of the leaf drivers. If leaf > drivers are pulled in without that header, the drivers will fail to > build which will make people grumpy. Which is why I'm not suggesting doing that. > The suggestion of a separate branch that's added to over time as leaf > drivers become ready is even more work that a one-hit strategy. It will > also mean littering the working branch which a bunch more merges and/or > more frequent rebases than I'm happy with. As I said you don't *need* to do the separate branch, it's more of a nice to have in case cross tree issues come up, and it'll probably work fine most of the time to just put the incremental commits directly on your main branch even if there was a separate branch for the initial batch. This all becomes especially true as we get close to the merge window and the likelyhood of new cross tree issues decreases.
Attachment:
signature.asc
Description: PGP signature
