Re: [PATCH v2 0/6] Enable UFS support on Milos

["Martin K. Petersen" <martin.petersen@oracle.com>]

Hi Krzysztof!

> Driver subsystems CANNOT take DTS patches because DTS is independent
> hardware description, thus combining them implies dependency and
> usually means users can be silently affected. We expressed it many
> times and documented it in point 7 of [1] (although it does not need
> any documenting because it is different subsystem - why would you ever
> take arm64 stuff without acks/permission from its maintainers?)

I frequently add impending series to my staging tree. This is done to
see what breaks and what doesn't if I were to actually merge something.
Being in staging does not imply that things subsequently go into
scsi-queue. But obviously it does send the message that I am looking at
merging patches from a given series in near future.

My script tries to cherry-pick any commits from a series that are not
already in linux-next and which look relevant for the code to build and
run in a cross-compiled environment. The script is certainly not
perfect, figuring out cross-tree dependencies is not at all trivial. And
I certainly appreciate when submitters clearly indicate which patches
need to go through which tree. In this particular case there isn't a
dependency that would prevent me from building the code that I actually
merge. But that isn't always the case. And I clearly need to be able to
build and validate the patches I subsequently put in scsi-queue.

I'll try to make my script more iterative and only backfill patches if
the build fails. Hopefully that'll resolve the situation...

-- 
Martin K. Petersen