DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, Paul Szczepanek <paul.szczepanek@arm.com>
Subject: Re: [PATCH v2 0/7] dts: shell improvements
Date: Thu, 24 Apr 2025 23:49:06 -0400	[thread overview]
Message-ID: <CAJvnSUBH_LQD6hoaMLXoY3=51gK4cCiEAbZLEH=41a1zSKzaKA@mail.gmail.com> (raw)
In-Reply-To: <20250314131857.1298247-1-luca.vizzarro@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

Thanks for this series Luca. Dean did a review earlier and I have just done
one so we're almost good to proceed. I should probably apply it and do a
testrun before merging, which should be possible tomorrow (Friday).

I will flag that when I tried to apply the series, git complained of a sha1
issue:

Applying: dts: escape single quotes
Applying: dts: add blocking dpdk app class
Applying: dts: add shells pool
Applying: dts: revert back to a single InteractiveShell
error: sha1 information is lacking or useless
(dts/framework/remote_session/testpmd_shell.py).
error: could not build fake ancestor
Patch failed at 0004 dts: revert back to a single InteractiveShell

From a quick google, it sounds like this can happen when sharing
commits/patches across related repos, when one of the repos has rewritten
history. Maybe this is because sometimes dpdk mainline rewords commits and
then we hard reset off of that... or some other reason - not sure right
now. But in any case it sounds like it's benign and there are some
tricks/workarounds to apply it so it probably won't be an issue. If it is
I'll let you know. :)

Thanks.

[-- Attachment #2: Type: text/html, Size: 1289 bytes --]

      parent reply	other threads:[~2025-04-25  3:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:23 [RFC PATCH 0/2] dts: add basic scope to improve shell handling Luca Vizzarro
2024-12-20 17:24 ` [RFC PATCH 1/2] dts: add scoping and shell registration to Node Luca Vizzarro
2024-12-20 17:24 ` [RFC PATCH 2/2] dts: revert back shell split Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 0/7] dts: shell improvements Luca Vizzarro
2025-03-14 13:18   ` [PATCH v2 1/7] dts: escape single quotes Luca Vizzarro
2025-04-24 17:55     ` Dean Marx
2025-04-25  2:20     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 2/7] dts: add blocking dpdk app class Luca Vizzarro
2025-04-24 18:01     ` Dean Marx
2025-04-25  2:38     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 3/7] dts: add shells pool Luca Vizzarro
2025-04-24 18:15     ` Dean Marx
2025-04-25  3:06     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 4/7] dts: revert back to a single InteractiveShell Luca Vizzarro
2025-04-24 18:22     ` Dean Marx
2025-04-25  3:26     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 5/7] dts: make shells path dynamic Luca Vizzarro
2025-04-24 18:29     ` Dean Marx
2025-04-25  3:31     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 6/7] dts: remove multi-inheritance classes Luca Vizzarro
2025-04-24 18:36     ` Dean Marx
2025-04-25  3:36     ` Patrick Robb
2025-03-14 13:18   ` [PATCH v2 7/7] dts: enable shell pooling Luca Vizzarro
2025-04-24 18:40     ` Dean Marx
2025-04-25  3:41     ` Patrick Robb
2025-04-25  3:49   ` Patrick Robb [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='CAJvnSUBH_LQD6hoaMLXoY3=51gK4cCiEAbZLEH=41a1zSKzaKA@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=dev@dpdk.org \
    --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 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).