DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Patrick Robb <probb@iol.unh.edu>, "dev@dpdk.org" <dev@dpdk.org>,
	"dts@dpdk.org" <dts@dpdk.org>, nd <nd@arm.com>
Subject: Re: DTS WG Meeting Minutes - August 1, 2024
Date: Fri, 02 Aug 2024 16:45:41 +0200	[thread overview]
Message-ID: <1996587.usQuhbGJ8B@thomas> (raw)
In-Reply-To: <8036F6F7-7544-42A8-8ECF-DEA7E528F995@arm.com>

02/08/2024 16:31, Honnappa Nagarahalli:
> 
> > On Aug 2, 2024, at 8:34 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
> > 
> > 01/08/2024 21:39, Patrick Robb:
> >> * Do we want to add DTS items to release notes?
> >>   * What is the process for building the release notes? Should the
> >> people working on DTS aggregate the updates and submit them? Patrick
> >> Robbshould check the website for the release notes process, or email
> >> the dev mailing list asking.
> > 
> > The release notes are part of the builtin documentation.
> > It should be updated atomically while adding a feature,
> > i.e. this file should be updated in the same patch as the related DTS code.
> > 
> > If any questions, please ask.
> I guess we should add a new section for DTS in the release notes?

There is no section, it just has to be added at the end in "New Features",
as tooling is usually sorted at the end.



      reply	other threads:[~2024-08-02 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 19:39 Patrick Robb
2024-08-02 13:34 ` Thomas Monjalon
2024-08-02 14:31   ` Honnappa Nagarahalli
2024-08-02 14:45     ` Thomas Monjalon [this message]

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=1996587.usQuhbGJ8B@thomas \
    --to=thomas@monjalon.net \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=nd@arm.com \
    --cc=probb@iol.unh.edu \
    /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).