On 1/19/22 9:47 AM, Wolfram Sang wrote:
I considered sending the request_muxed_mem_region() patch series first but
was concerned the patch might not be accepted without a need or usage. I
didn't see an obvious path forward for the order of submissions because of
the dependencies.
My suggestion: make the request_muxed_mem_region() patch the new patch 1
of the piix4 series. Then, the user will directly come in the following
patches. From this series, I will create an immutable branch which can
be pulled in by the watchdog tree. It will then have the dependency for
your watchdog series. During next merge window, we (the maintainers)
will make sure that I2C will hit Linus' tree before the watchdog tree.
This works the other way around as well, if needed. Make
request_muxed_mem_region() the first patch of the watchdog series and
let me pull an immutable branch from watchdog into I2C.
Creating an immutable branch from i2c is fine. Also, typically Wim sends
his pull request late in the commit window, so i2c first should be no
problem either.
Also, if the immutable branch only includes the patch introducing
request_muxed_mem_region(), the pull order should not really matter.
Guenter
