DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>,
	"Lijuan Tu" <lijuan.tu@intel.com>,
	"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Owen Hilyard" <ohilyard@iol.unh.edu>, nd <nd@arm.com>,
	nd <nd@arm.com>
Subject: RE: DTS WG meeting minutes - 1/12/22
Date: Fri, 21 Jan 2022 00:48:38 +0000	[thread overview]
Message-ID: <DBAPR08MB58144A83A789DDD7CF5F1C19985B9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <YeknJbhHser9rxfP@bricha3-MOBL.ger.corp.intel.com>

<snip>

> > DTS. Will be discussed when Lincoln and Juraj are available 5) The DTS
> > user guide and DTS test plans are being built using makefile. This
> > needs to be changed to using meson build.
> >
> For this point #5, not knowing the details here, but at a high level, I wonder if
> that really needs to be done, if the existing make build of the doc works ok. As
> the plan is to move DTS into DPDK repo, presumably the documentation would
> also move, and at that point it can just reuse the DPDK meson build
> infrastructure for documentation. Is there a compelling reason to invest in
> doing this change earlier? For docs rather than code, moving to meson doesn't
> generally give much benefit - the only reason we did so in main DPDK repo was
> consistency with everything else.
Thanks Bruce for the comments.
The reason for considering this was to stay consistent with DPDK and the changes seem to be small.

IMO (it still need to be discussed in WG), the DTS will stay separated from the rest of the code (though under the same repo). For ex: the documentation building might not be integrated with DPDK doc build. This will ensure that DPDK doc build times are not affected. But, we could have a different target to build DTS doc at the root level.

It makes sense to differ this to a later point.
 
> 
> /Bruce

      reply	other threads:[~2022-01-21  0:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 21:25 Honnappa Nagarahalli
2022-01-20  9:11 ` Bruce Richardson
2022-01-21  0:48   ` Honnappa Nagarahalli [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=DBAPR08MB58144A83A789DDD7CF5F1C19985B9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=ohilyard@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).