From: Patrick Robb <probb@iol.unh.edu>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>,
ci@dpdk.org, Paul Szczepanek <Paul.Szczepanek@arm.com>
Subject: Dev branch on next-dts
Date: Thu, 6 Mar 2025 12:58:17 -0500 [thread overview]
Message-ID: <CAJvnSUBEu56v8a27m8BTXTgRB9-n=z6xnHVewtzS8mGCDFo8gA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Hi Thomas/David,
We still have a couple patchseries under review for next-dts which we
intend to push to next-dts/for-main, to be pulled for 25.03. At the same
time, there are some series which we are working on but are now pushed to
the 25.07 release. We want to continue to work on these over the next few
weeks, but don't want to push them to for-main obviously.
Paul (DTS tree maintainer) has suggested that we create a dev branch on
dpdk-next-dts for this. It sounds fine to me - I am just running it by you
both so you are aware.
We'll go ahead in case you have any concerns. Cheers!
-Patrick
[-- Attachment #2: Type: text/html, Size: 745 bytes --]
reply other threads:[~2025-03-06 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJvnSUBEu56v8a27m8BTXTgRB9-n=z6xnHVewtzS8mGCDFo8gA@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Paul.Szczepanek@arm.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).