From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: workflows@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
Subject: Depends-on tag
Date: Wed, 28 May 2025 07:19:55 -0700 [thread overview]
Message-ID: <67f86f2e-d3ac-4fbe-87d6-186487de5721@oss.qualcomm.com> (raw)
patchwork itself very recently formalized the usage of a 'Depends-on:' tag for
flagging patchset dependencies:
https://lists.ozlabs.org/pipermail/patchwork/2025-January/007465.html
https://lists.ozlabs.org/pipermail/patchwork/2025-March/007490.html
https://github.com/getpatchwork/patchwork/commit/bc2d1b1dcf89c619e027ae4dfd3036cba30e5583
https://patchwork.ozlabs.org/project/patchwork/list/?series=442332&state=*
Note that this support is only in mainline and not part of any release yet.
Curious if the Linux Kernel community will adopt this approach for flagging
dependencies.
/jeff
next reply other threads:[~2025-05-28 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 14:19 Jeff Johnson [this message]
2025-05-28 15:22 ` Konstantin Ryabitsev
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=67f86f2e-d3ac-4fbe-87d6-186487de5721@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=aditya.kumar.singh@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=workflows@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