DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	 Paul Szczepanek <paul.szczepanek@arm.com>
Subject: Re: [PATCH v2 1/2] dts: improve documentation
Date: Tue, 16 Jan 2024 17:47:46 +0100	[thread overview]
Message-ID: <CAOb5WZYcPmOpSnC3+6Wv-3Z937MCs11g11H7BjcEcDYGjAisQQ@mail.gmail.com> (raw)
In-Reply-To: <20240116114449.486708-1-luca.vizzarro@arm.com>

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

On Tue, Jan 16, 2024 at 12:46 PM Luca Vizzarro <luca.vizzarro@arm.com> wrote:
>
> Improve instructions for installing dependencies, configuring and
> launching the project. Add mypy in the list of developer tools.
>
> Finally, fix a bug where Poetry expects to install DTS as a package
> as well while resolving the dependencies. Because DTS is not setup
> as a package, this results in an error raised.
>
> Reviewed-by: Paul Szczepanek <paul.szczepanek@arm.com>
> Signed-off-by: Luca Vizzarro <luca.vizzarro@arm.com>

  parent reply	other threads:[~2024-01-16 16:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 12:54 [PATCH] " Luca Vizzarro
2024-01-04 10:52 ` Thomas Monjalon
2024-01-04 12:34   ` Luca Vizzarro
2024-01-04 13:15     ` Thomas Monjalon
2024-01-12 13:24 ` Juraj Linkeš
2024-01-12 17:16   ` Luca Vizzarro
2024-01-15  9:36     ` Juraj Linkeš
2024-01-15 11:44       ` Luca Vizzarro
2024-01-16 11:44 ` [PATCH v2 1/2] " Luca Vizzarro
2024-01-16 11:44   ` [PATCH v2 2/2] dts: add configuration schema docs Luca Vizzarro
2024-01-16 16:48     ` Juraj Linkeš
2024-01-16 16:47   ` Juraj Linkeš [this message]
2024-01-19 17:29     ` [PATCH v2 1/2] dts: improve documentation 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=CAOb5WZYcPmOpSnC3+6Wv-3Z937MCs11g11H7BjcEcDYGjAisQQ@mail.gmail.com \
    --to=juraj.linkes@pantheon.tech \
    --cc=dev@dpdk.org \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@arm.com \
    --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).