From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
<linux-sound@vger.kernel.org>
Subject: Question: layout of a patchset dependent on another tree
Date: Thu, 18 Apr 2024 13:43:25 +0200 [thread overview]
Message-ID: <2d1980e9-f5b2-4c9e-9348-af69166d0882@intel.com> (raw)
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
next reply other threads:[~2024-04-18 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 11:43 Cezary Rojewski [this message]
2024-04-19 1:25 ` Question: layout of a patchset dependent on another tree Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d1980e9-f5b2-4c9e-9348-af69166d0882@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).