All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Alex Chapman <alex.chapman@arm.com>
Cc: dev@dpdk.org,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Jack Bond-Preston" <jack.bond-preston@arm.com>,
	"Luca Vizzarro" <luca.vizzarro@arm.com>,
	"Paul Szczepanek" <paul.szczepanek@arm.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: Re: [PATCH] dts: fix DPDK git tarball cast bug
Date: Tue, 23 Jul 2024 23:43:35 +0200	[thread overview]
Message-ID: <1992982.usQuhbGJ8B@thomas> (raw)
In-Reply-To: <54c4165b-d986-4751-9907-9b54bb52a7b4@pantheon.tech>

22/07/2024 15:06, Juraj Linkeš:
> 
> On 19. 7. 2024 17:34, Alex Chapman wrote:
> > When running DTS with a git revision specified the following error occurs:
> > $ ./main.py --revision HEAD
> > [...]
> > FileNotFoundError: [Errno 2] No such file or directory:
> >       'dts/<framework.utils.DPDKGitTarball object at 0x78f69e73a5c0>'
> > 
> > Fix by casting DPDKGitTarball to Path, in order to stringify it correctly.
> > 
> > Bugzilla ID: 1496
> > Fixes: a23f22457dbd ("dts: constrain DPDK source argument")
> > 
> > Signed-off-by: Alex Chapman <alex.chapman@arm.com>
> > Reviewed-by: Jack Bond-Preston <jack.bond-preston@arm.com>
> > Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
> > Reviewed-by: Paul Szczepanek <paul.szczepanek@arm.com>
> > ---
> > Hello,
> > Sending this fix to a bug that i discovered.
> > 
> > Best Regards,
> > Alex
> > ---
> Reviewed-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> 
> Thanks for catching this.

Applied, thanks and welcome.




      reply	other threads:[~2024-07-23 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 15:34 [PATCH] dts: fix DPDK git tarball cast bug Alex Chapman
2024-07-22 13:06 ` Juraj Linkeš
2024-07-23 21:43   ` 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=1992982.usQuhbGJ8B@thomas \
    --to=thomas@monjalon.net \
    --cc=alex.chapman@arm.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jack.bond-preston@arm.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.