[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3mp746jccer7dbn4ra4h5ag66d7dn7gqebriwliicdgzevrmgn@lir2lwtnlbhz>
Date: Mon, 28 Aug 2023 19:03:18 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Bart Van Assche <bvanassche@....org>
Cc: linux-nvme@...ts.infradead.org, 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 Mon, Aug 28, 2023 at 08:14:09AM -0700, Bart Van Assche wrote:
> 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?
Sure, I'll add a warning.
Powered by blists - more mailing lists