mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Serge Semin <fancer.lancer@gmail.com>,
	jdmason@kudzu.us, dave.jiang@intel.com, Allen.Hubbe@emc.com,
	Shyam-sundar.S-k@amd.com, Xiangliang.Yu@amd.com
Cc: Sergey.Semin@t-platforms.ru, linux-ntb@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/08] NTB: ntb_test: Add ntb_tool port tests
Date: Thu, 30 Nov 2017 15:37:13 -0700	[thread overview]
Message-ID: <5f9198e4-24d4-88f5-89d2-d36c5afa76ef@deltatee.com> (raw)
In-Reply-To: <20171130214300.21298-2-fancer.lancer@gmail.com>


On 30/11/17 02:42 PM, Serge Semin wrote:
> +function find_pidx()
> +{
> +	PORT=$1
> +	PPATH=$2
> +
> +	for ((i = 0; i < 64; i++)); do
> +		PEER_DIR="$PPATH/peer$i"
> +
> +		check_file ${PEER_DIR} || break
> +
> +		PEER_PORT=$(read_file "${PEER_DIR}/port")
> +		if [[ ${PORT} -eq $PEER_PORT ]]; then
> +			echo $i
> +			return 0
> +		fi
> +	done
> +
> +	return 1
> +}

Actually, per my earlier comments on other messages. I think it would be 
best if each of the patches in this series also included the relevant 
changes to ntb_tool. Then just ditch the ntb_tool patch. For example, 
this patch would include adding the "port" file to ntb_tool and the 
relevant test to ntb_test.

Otherwise, when the ntb_tool patch is committed, the ntb_test breaks and 
then is fixed in subsequent patches. In an ideal world, this would be 
avoided in case we ever want to do a bisect involving ntb_test.

Logan

  reply	other threads:[~2017-11-30 22:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 21:42 [PATCH 01/08] NTB: ntb_test: Safely use paths with whitespace Serge Semin
2017-11-30 21:42 ` [PATCH 02/08] NTB: ntb_test: Add ntb_tool port tests Serge Semin
2017-11-30 22:37   ` Logan Gunthorpe [this message]
2017-11-30 21:42 ` [PATCH 03/08] NTB: ntb_test: Update ntb_tool link tests Serge Semin
2017-11-30 21:42 ` [PATCH 04/08] NTB: ntb_test: Update ntb_tool DB tests Serge Semin
2017-11-30 21:42 ` [PATCH 05/08] NTB: ntb_test: Update ntb_tool Scratchpad tests Serge Semin
2017-11-30 21:42 ` [PATCH 06/08] NTB: ntb_test: Add ntb_tool Message tests Serge Semin
2017-11-30 21:42 ` [PATCH 07/08] NTB: ntb_test: Update ntb_tool MW tests Serge Semin
2017-11-30 21:43 ` [PATCH 08/08] NTB: ntb_test: Update ntb_perf tests Serge Semin
2017-11-30 22:04 ` [PATCH 01/08] NTB: ntb_test: Safely use paths with whitespace Logan Gunthorpe
2017-11-30 22:12   ` Serge Semin
2017-11-30 22:26     ` Logan Gunthorpe

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=5f9198e4-24d4-88f5-89d2-d36c5afa76ef@deltatee.com \
    --to=logang@deltatee.com \
    --cc=Allen.Hubbe@emc.com \
    --cc=Sergey.Semin@t-platforms.ru \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=Xiangliang.Yu@amd.com \
    --cc=dave.jiang@intel.com \
    --cc=fancer.lancer@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntb@googlegroups.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

all inboxes | Powered by JetHome®