* Question: layout of a patchset dependent on another tree
@ 2024-04-18 11:43 Cezary Rojewski
2024-04-19 1:25 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Cezary Rojewski @ 2024-04-18 11:43 UTC (permalink / raw
To: Mark Brown; +Cc: alsa-devel@alsa-project.org, linux-sound
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Question: layout of a patchset dependent on another tree
2024-04-18 11:43 Question: layout of a patchset dependent on another tree Cezary Rojewski
@ 2024-04-19 1:25 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2024-04-19 1:25 UTC (permalink / raw
To: Cezary Rojewski; +Cc: alsa-devel@alsa-project.org, linux-sound
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-04-19 1:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-04-18 11:43 Question: layout of a patchset dependent on another tree Cezary Rojewski
2024-04-19 1:25 ` Mark Brown
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 read-only IMAP folder(s) and NNTP newsgroup(s).