Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1885155pxb; Mon, 22 Feb 2021 13:40:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJyWGYBAexIurZ0RryB+rWpZoO8JJLIg7NCC7ZZ+bl/Eb97ZCJtUK+2GV0TmXE5XxRvrErbZ X-Received: by 2002:aa7:cac6:: with SMTP id l6mr25455235edt.357.1614030053102; Mon, 22 Feb 2021 13:40:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614030053; cv=none; d=google.com; s=arc-20160816; b=kP5ENsU5/3YYam8CA8goL1ajb9F4Hl+nA+dvl3rHgKXB66fOfClNpxynmiwblC6c4w /2imEqH/OeKNDqUSxKHUxeCWL/GqV3iF/tMllx8SdJkTyf994BeEfMIypMVZiBsInUYr 85g370SIgbTwoszMwZWMuVye9fEzZV+Zw+8EGREUxSjg8IBCisBgTjxLBz4lve6xW2ak 4soxA/l1tAlzk2q25eXq2huwNNRZRtVx/rySeHcrT3qzMxjdBPy3zgll35NUVf2gk2lR 5tb6AZl8qK6KJzbkgfE0MFh7dcnrUOK2tgbWr1MZ4iu+GpMaGlx18uSjPPb40c3KZaO3 sKaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature:dkim-filter; bh=bL4sbefqoOVp9OCqDyDEVtsiOHFV5JJR/crNNp2k3pM=; b=lTakrLfoUZd2/+o6Y9Xyul1kCrwE/NQRZMMU6mevV2c0F/smZ6Noj40iY8EN+XPY8p Sm3NrayS6xUlaZzGC3XMQuOTYFCGcoXKGkoc145uvIQ/H/ZbovCRCCWGazya034L1pjo /5o+8CcejtnSc2KkEQ1/v5Ocmjr7hzJpOXHpRglfQ8GS0cVPmF9dOgoEq4LL0JfJd/Gi 7LxSCG58owTqDSBACQvxywJUC1A0zvQk70A2gRMyKGSzViVhKQwDLXYct5bI2E6IShFy HUOwI65T+BFCynA0IG+yVkEnc9DIccCIHCcEtWChXBReYogL5MN1cl1cE4n+QwUiofym 5+Rw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=VKmOuPKu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h5si12434318edd.175.2021.02.22.13.40.30; Mon, 22 Feb 2021 13:40:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=VKmOuPKu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230514AbhBVVe1 (ORCPT + 99 others); Mon, 22 Feb 2021 16:34:27 -0500 Received: from ms.lwn.net ([45.79.88.28]:35046 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230063AbhBVVeY (ORCPT ); Mon, 22 Feb 2021 16:34:24 -0500 Received: from localhost (unknown [IPv6:2601:281:8300:104d::5f6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 0FB7B2B7; Mon, 22 Feb 2021 21:33:33 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 0FB7B2B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1614029613; bh=bL4sbefqoOVp9OCqDyDEVtsiOHFV5JJR/crNNp2k3pM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=VKmOuPKu3fJG5P5HH+PnRU/+xrc8DgTCfef6J3Gozkc/h7IU1qRRHZRQ86K3faEae XK02k7S+AJnH69MywGMCq5CPy91M+pW7TsNc6Wf1CWC3d+CM/uyoMaQo+hOM+nKG1q sLvELn44CiV5xcL04T6edwL5I2ANJ3TGAM+BpYbut3h7l+Sbk9FLBjzgw766QNH5BS iuXCncnezFRYMJM4BpunAwJ8cZVeqRSSoMIb3i4506nsvfSHBA65ZKs10sNmEnzHMj JsY2R7g7R5+RGcg+1xrqygBkSX8fR/TR3Jv8rggMpzLzwG4ULlhV1HdBQHSJaZoRvY PhwwVmINpkNqg== From: Jonathan Corbet To: Aditya Srivastava Cc: yashsri421@gmail.com, lukas.bulwahn@gmail.com, linux-kernel-mentees@lists.linuxfoundation.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [RFC] scripts: kernel-doc: fix array element capture in pointer-to-func parsing In-Reply-To: <20210217145625.14006-1-yashsri421@gmail.com> References: <20210217145625.14006-1-yashsri421@gmail.com> Date: Mon, 22 Feb 2021 14:33:32 -0700 Message-ID: <878s7flrdf.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Aditya Srivastava writes: > Currently, kernel-doc causes an unexpected error when array element (i.e., > "type (*foo[bar])(args)") is present as pointer parameter in > pointer-to-function parsing. > > For e.g., running kernel-doc -none on kernel/gcov/gcc_4_7.c causes this > error: > "Use of uninitialized value $param in regexp compilation at ...", in > combination with: > "warning: Function parameter or member '' not described in 'gcov_info'" In the future, please quote error messages from the kernel verbatim. You can trim irrelevant stuff before or after, but please do not edit them in this way. That helps me to understand what you are fixing, and is also useful for anybody else who might be searching for a solution to the same problem. > Here, the parameter parsing does not take into account the presence of > array element (i.e. square brackets) in $param. > > Provide a simple fix by adding square brackets in the regex, responsible > for capturing $param. > > A quick evaluation, by running 'kernel-doc -none' on entire kernel-tree, > reveals that no additional warning or error has been added or removed by > the fix. > > Suggested-by: Lukas Bulwahn > Signed-off-by: Aditya Srivastava > --- > * Applies perfectly over next-20210217 > > scripts/kernel-doc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/scripts/kernel-doc b/scripts/kernel-doc > index e046e16e4411..8b5bc7bf4bb8 100755 > --- a/scripts/kernel-doc > +++ b/scripts/kernel-doc > @@ -1553,7 +1553,7 @@ sub create_parameterlist($$$$) { > } elsif ($arg =~ m/\(.+\)\s*\(/) { > # pointer-to-function > $arg =~ tr/#/,/; > - $arg =~ m/[^\(]+\(\*?\s*([\w\.]*)\s*\)/; > + $arg =~ m/[^\(]+\(\*?\s*([\w\[\]\.]*)\s*\)/; > $param = $1; > $type = $arg; > $type =~ s/([^\(]+\(\*?)\s*$param/$1/; > -- ...meanwhile, I have applied this one, thanks. jon