From: Petr Machata <petrm@nvidia.com>
To: Petr Machata <petrm@nvidia.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
<netdev@vger.kernel.org>, Danielle Ratson <danieller@nvidia.com>
Subject: Re: [RFC PATCH net-next] selftests: forwarding: add a test for MAC Merge layer
Date: Mon, 20 Mar 2023 14:49:37 +0100 [thread overview]
Message-ID: <87jzzbplzk.fsf@nvidia.com> (raw)
In-Reply-To: <871qlnqt7k.fsf@nvidia.com>
Petr Machata <petrm@nvidia.com> writes:
> Petr Machata <petrm@nvidia.com> writes:
>
>> I added a shim as shown below. Comments welcome. Your patch then needs a
>> bit of adaptation, plus I've dropped all the now-useless imports of
>> qos_lib.sh. I'll pass this through our regression, and if nothing
>> explodes, I'll point you at a branch tomorrow, and you can make the two
>> patches a part of your larger patchset?
>
> (I only pushed this to our regression today. The patches are the top two
> ones here:
>
> https://github.com/pmachata/linux_mlxsw/commits/petrm_selftests_bail_on_lldpad_move
>
> I'll let you know on Monday whether anything exploded in regression.)
Nothing _relevant_ seems to have exploded :)
I've pushed a new version of the patches with Danielle's (CC'd) R-b tags
and a fix of a typo that she noticed. Feel free to take these and
integrate / adjust / etc.
next prev parent reply other threads:[~2023-03-20 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:12 [RFC PATCH net-next] selftests: forwarding: add a test for MAC Merge layer Vladimir Oltean
2023-02-13 10:51 ` Petr Machata
2023-02-13 11:39 ` Vladimir Oltean
2023-02-14 11:53 ` Petr Machata
2023-03-15 15:52 ` Vladimir Oltean
2023-03-16 11:10 ` Petr Machata
2023-03-16 13:43 ` Petr Machata
2023-03-17 15:35 ` Petr Machata
2023-03-17 15:45 ` Vladimir Oltean
2023-03-20 10:20 ` Petr Machata
2023-03-20 13:49 ` Petr Machata [this message]
2023-02-13 11:42 ` Kurt Kanzenbach
2023-02-13 12:02 ` Vladimir Oltean
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=87jzzbplzk.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=danieller@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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.