DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Dean Marx <dmarx@iol.unh.edu>, Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org, luca.vizzarro@arm.com, yoan.picchi@foss.arm.com,
	Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com,
	dev@dpdk.org
Subject: Re: [PATCH v2 2/2] dts: rewrite dts rst
Date: Wed, 09 Jul 2025 21:57:24 +0200	[thread overview]
Message-ID: <3827624.axiByQ7kbq@thomas> (raw)
In-Reply-To: <CAJvnSUAGND5nTFHp71_d4ELqY20bcLC8Oc-OAhWz0V1jcpvOhA@mail.gmail.com>

25/06/2025 06:07, Patrick Robb:
> Applied to next-dts, thanks Dean.

I'm almost sure it has overriden some doc added recently by Nicholas Pratte.

Anyway it is too difficult to understand what is changed in this series,
because there are too many unrelated changes.

I prefer not pulling this series in the main branch for now.
Please split the patches with clear explanation of what is changed and why.

Thanks



  reply	other threads:[~2025-07-09 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 15:37 [PATCH v1 1/3] dts: rewrite README Dean Marx
2025-05-27 15:37 ` [PATCH v1 2/3] dts: rewrite dts rst Dean Marx
2025-05-28 21:25   ` Patrick Robb
2025-05-29 12:27     ` Paul Szczepanek
2025-06-03 17:28   ` [PATCH v2 1/2] dts: rewrite README Dean Marx
2025-06-03 17:28     ` [PATCH v2 2/2] dts: rewrite dts rst Dean Marx
2025-06-25  4:07       ` Patrick Robb
2025-07-09 19:57         ` Thomas Monjalon [this message]
2025-06-25  4:06     ` [PATCH v2 1/2] dts: rewrite README Patrick Robb
2025-05-27 15:37 ` [PATCH v1 3/3] dts: fix doc generation bug Dean Marx
2025-05-28 20:28   ` Patrick Robb
2025-05-29 12:28     ` Paul Szczepanek
2025-05-28 20:40 ` [PATCH v1 1/3] dts: rewrite README Patrick Robb
2025-05-29 12:27   ` Paul Szczepanek
2025-05-29 12:40 ` Paul Szczepanek

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=3827624.axiByQ7kbq@thomas \
    --to=thomas@monjalon.net \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=yoan.picchi@foss.arm.com \
    /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).