Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Abhinav Jain <jain.abhinav177@gmail.com>
To: kuba@kernel.org
Cc: davem@davemloft.net, edumazet@google.com,
	jain.abhinav177@gmail.com, javier.carrasco.cruz@gmail.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com, shuah@kernel.org,
	skhan@linuxfoundation.org
Subject: Re: [PATCH v8 net-next 1/3] selftests: net: Create veth pair for testing in networkless kernel
Date: Wed, 21 Aug 2024 22:51:46 +0530	[thread overview]
Message-ID: <20240821172146.118441-1-jain.abhinav177@gmail.com> (raw)
In-Reply-To: <20240821090041.53df4147@kernel.org>

On Wed, 21 Aug 2024 09:00:41 -0700, Jakub Kicinski wrote:
>> I presumed that we would want to run the interface up/down, setup and ethtool tests on both veth.
>> If this is not required, should I submit a v9 removing veth1 from the temp list?
>
> Yes, please.
>
>> Also, while sending v9, do I add the Review tag from Simon or it has to be reviewed again?
> 
> Yes, you should add the review tags

Thanks for confirming, I have sent v9 accordingly:
https://lore.kernel.org/all/20240821171903.118324-1-jain.abhinav177@gmail.com

Please review, thanks again.

  reply	other threads:[~2024-08-21 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 12:12 [PATCH v8 net-next 0/3] Enhance network interface feature testing Abhinav Jain
2024-08-19 12:12 ` [PATCH v8 net-next 1/3] selftests: net: Create veth pair for testing in networkless kernel Abhinav Jain
2024-08-19 15:02   ` Simon Horman
2024-08-20 23:50   ` Jakub Kicinski
2024-08-21 12:37     ` Abhinav Jain
2024-08-21 16:00       ` Jakub Kicinski
2024-08-21 17:21         ` Abhinav Jain [this message]
2024-08-19 12:12 ` [PATCH v8 net-next 2/3] selftests: net: Add on/off checks for non-fixed features of interface Abhinav Jain
2024-08-19 15:03   ` Simon Horman
2024-08-19 12:12 ` [PATCH v8 net-next 3/3] selftests: net: Use XFAIL for operations not supported by the driver Abhinav Jain
2024-08-19 15:03   ` Simon Horman

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=20240821172146.118441-1-jain.abhinav177@gmail.com \
    --to=jain.abhinav177@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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