Question: layout of a patchset dependent on another tree

Question: layout of a patchset dependent on another tree

[Cezary Rojewski]

Hello Mark,

I'd like to send changes which do modify the avs-driver but are 
dependent on ACPI/NHLT changes I've recently upstream [1] to Rafael's 
linux-acpi tree. Thanks to Rafael, there's an immutable branch [2] that 
has all relevant commits on the top.

Should I send both the NHLT+avs changes and have broonie/for-next as a 
base for that or provide only the avs changes and state the dependency 
within the cover-letter? The latter will fail to compile without its 
dependency obviously.


[1]: 
https://lore.kernel.org/linux-acpi/20240319083018.3159716-1-cezary.rojewski@intel.com/
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/log/?h=acpi-nhlt

Kind regards,
Czarek

Re: Question: layout of a patchset dependent on another tree

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

On Thu, Apr 18, 2024 at 01:43:25PM +0200, Cezary Rojewski wrote:

> I'd like to send changes which do modify the avs-driver but are dependent on
> ACPI/NHLT changes I've recently upstream [1] to Rafael's linux-acpi tree.
> Thanks to Rafael, there's an immutable branch [2] that has all relevant
> commits on the top.

> Should I send both the NHLT+avs changes and have broonie/for-next as a base
> for that or provide only the avs changes and state the dependency within the
> cover-letter? The latter will fail to compile without its dependency
> obviously.

I'd send based on the immutable branch so long as that will merge into
my tree easily enough (doesn't have to be perfect).  If it needs the
immutable branch merging into the ASoC tree first then I'd send based on
that merge with a note in the cover letter explaining this.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]