From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B83AEB64D9 for ; Tue, 4 Jul 2023 14:45:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230052AbjGDOpy (ORCPT ); Tue, 4 Jul 2023 10:45:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55870 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229610AbjGDOpx (ORCPT ); Tue, 4 Jul 2023 10:45:53 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0DB17E49 for ; Tue, 4 Jul 2023 07:45:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1688481952; x=1720017952; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=kAgvHoyepNldKY2kVJ9tpLH/o3qdQ55Z+tiksdlAXpM=; b=VOZkqbTQFw0kQ6QKCp+blktfXXu0t57yETfwonvABAhKB7Vd72qCwvxZ +6zXV/1YhVWxJ6T3/qUw7K67xSKq147mUzWeN5Ou/M2wEKf/yden8VPKn WYRQJ5oV1pc5f2usVCXqIScrYUU8SM0VBdPNa9lBAe6xRejaJtqK2kLnv 3AcxiDefOOqoiCsaCM6DswSzMp9a3VQ2MeJqJBlGiKNYu/ZlWUDXJ4t+c BLKazQ52+m8UHuc6rAVa9+ldps6UjPXskNmiqNFdNIpL5L5XQJUifhHA9 rM4lqcvpyj8wbwkU6kNqwNTpy2NIRwitNJDGV40F2MKj5PmE8+g78PJlX A==; X-IronPort-AV: E=McAfee;i="6600,9927,10760"; a="429174891" X-IronPort-AV: E=Sophos;i="6.01,180,1684825200"; d="scan'208";a="429174891" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jul 2023 07:45:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10760"; a="748440587" X-IronPort-AV: E=Sophos;i="6.01,181,1684825200"; d="scan'208";a="748440587" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga008.jf.intel.com with ESMTP; 04 Jul 2023 07:45:43 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qGhHh-0002w3-39; Tue, 04 Jul 2023 17:45:41 +0300 Date: Tue, 4 Jul 2023 17:45:41 +0300 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Kent Gibson , Linus Walleij , Viresh Kumar , linux-gpio@vger.kernel.org, Bartosz Golaszewski Subject: Re: [libgpiod][PATCH] tools: clarify the non-option arguments in help text Message-ID: References: <20230704121222.314617-1-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230704121222.314617-1-brgl@bgdev.pl> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, Jul 04, 2023 at 02:12:22PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > We already use [] for optional and <> for required arguments in help text > but let's make it clear that we can pass multiple chips/lines and in most > tools only the first one is required. I agree with Kent, I prefer the former over the latter. And with this syntax the reality looks as [chip1 [chip2] ...] rather than ambiguous [x] [y] where I can't understand what is the meaning of the chip1 be omitted while chip2 is present. -- With Best Regards, Andy Shevchenko