All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Hongzhan Chen <hongzhan.chen@intel.com>, xenomai@xenomai.org
Subject: Re: [PATCH V2] testsuite/smokey: net: load rtnet module if it has not been loaded
Date: Thu, 5 Aug 2021 07:00:38 +0200	[thread overview]
Message-ID: <06d98602-f257-518c-aac2-8f4378ac14bc@siemens.com> (raw)
In-Reply-To: <20210805031327.10873-1-hongzhan.chen@intel.com>

On 05.08.21 05:13, Hongzhan Chen via Xenomai wrote:
> Before checking net config, rtnet should be ready.
> 
> Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
> 
> diff --git a/testsuite/smokey/net_common/setup.c b/testsuite/smokey/net_common/setup.c
> index 1badabdfb..a0512b00d 100644
> --- a/testsuite/smokey/net_common/setup.c
> +++ b/testsuite/smokey/net_common/setup.c
> @@ -408,6 +408,10 @@ int smokey_net_setup(const char *driver, const char *intf, int tested_config,
>  	struct sockaddr_in *in_peer = vpeer;
>  	struct sockaddr *peer = vpeer;
>  
> +	err = smokey_net_modprobe(MODID_RTNET);
> +	if (err < 0)
> +		return err;
> +
>  	err = cobalt_corectl(_CC_COBALT_GET_NET_CONFIG,
>  			&net_config, sizeof(net_config));
>  	if (err == -EINVAL)
> 

Sorry, only realized now: The checks that come right after this should
not be affected by rtnet being loaded or not yet. I think they check
whether it is configured and could be loaded. If we try to load when it
is not configured, the test case will fail rather than be skipped.
Please check and reorder the modprobe accordingly.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-08-05  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  3:13 [PATCH V2] testsuite/smokey: net: load rtnet module if it has not been loaded Hongzhan Chen
2021-08-05  5:00 ` Jan Kiszka [this message]
2021-08-05  5:21   ` Chen, Hongzhan
2021-08-05  5:25     ` Jan Kiszka
2021-08-05  5:32       ` Chen, Hongzhan
2021-08-05  5:50         ` Jan Kiszka
2021-08-05  6:12           ` Chen, Hongzhan
2021-08-05  8:10             ` Jan Kiszka

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=06d98602-f257-518c-aac2-8f4378ac14bc@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=hongzhan.chen@intel.com \
    --cc=xenomai@xenomai.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 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.