[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e407992-d6da-46e2-a006-ad3b3cdfb101@acm.org>
Date: Mon, 28 Aug 2023 08:14:09 -0700
From: Bart Van Assche <bvanassche@....org>
To: Daniel Wagner <dwagner@...e.de>, linux-nvme@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
Chaitanya Kulkarni <kch@...dia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>,
Hannes Reinecke <hare@...e.de>,
Sagi Grimberg <sagi@...mberg.me>,
Jason Gunthorpe <jgg@...pe.ca>
Subject: Re: [PATCH blktests v3 3/3] nvme: introduce
nvmet_target_{setup/cleanup} common code
On 8/22/23 01:38, Daniel Wagner wrote:
> + while [[ $# -gt 0 ]]; do
> + case $1 in
> + --blkdev)
> + blkdev_type="$2"
> + shift 2
> + ;;
> + --ctrlkey)
> + ctrlkey="$2"
> + shift 2
> + ;;
> + --hostkey)
> + hostkey="$2"
> + shift 2
> + ;;
> + *)
> + shift
> + ;;
> + esac
> + done
So all arguments that are not recognized are ignored? That will
make debugging typo's harder than necessary. Shouldn't this function
complain if an unrecognized argument is encountered?
Thanks,
Bart.
Powered by blists - more mailing lists