DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [PATCH] maintainers: add next DTS git repository
Date: Tue, 30 Jul 2024 13:00:32 +0200	[thread overview]
Message-ID: <c010e131-e86b-4e14-88f1-8b33a4a52640@pantheon.tech> (raw)
In-Reply-To: <20240730102134.631918-1-thomas@monjalon.net>

Acked-by: Juraj Linkeš <juraj.linkes@pantheon.tech>

On 30. 7. 2024 12:21, Thomas Monjalon wrote:
> The new repository dpdk-next-dts.git is maintained by Juraj,
> as approved by the Technical Board.
> DTS patches will prepared in a branch of this repository
> before being pulled in the main DPDK branch.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>   MAINTAINERS | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3e6bf0f8ae..c5a703b5c0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -64,6 +64,10 @@ Next-baseband Tree
>   M: Maxime Coquelin <maxime.coquelin@redhat.com>
>   T: git://dpdk.org/next/dpdk-next-baseband
>   
> +Next-dts Tree
> +M: Juraj Linkeš <juraj.linkes@pantheon.tech>
> +T: git://dpdk.org/next/dpdk-next-dts
> +
>   Stable Branches
>   M: Luca Boccassi <bluca@debian.org>
>   M: Kevin Traynor <ktraynor@redhat.com>
> @@ -1887,6 +1891,7 @@ F: doc/guides/tools/proc_info.rst
>   
>   DTS
>   M: Juraj Linkeš <juraj.linkes@pantheon.tech>
> +T: git://dpdk.org/next/dpdk-next-dts
>   F: dts/
>   F: devtools/dts-check-format.sh
>   F: doc/guides/tools/dts.rst

  reply	other threads:[~2024-07-30 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 10:21 Thomas Monjalon
2024-07-30 11:00 ` Juraj Linkeš [this message]
2024-07-30 11:23 ` Bruce Richardson
2024-07-30 15:32   ` Thomas Monjalon

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=c010e131-e86b-4e14-88f1-8b33a4a52640@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --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).