From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2] tools/find-api-violations: fix missing dirs in the directory list
Date: Wed, 25 Jan 2017 11:11:20 +0530 [thread overview]
Message-ID: <2357002.pCcJ9JlUn9@localhost.localdomain> (raw)
In-Reply-To: <20170125052852.GK9134@birch.djwong.org>
On Tuesday, January 24, 2017 09:28:52 PM Darrick J. Wong wrote:
> Fix a stupid typo in the original commit.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> tools/find-api-violations.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/find-api-violations.sh b/tools/find-api-violations.sh
> index 7937749..c2be4c5 100755
> --- a/tools/find-api-violations.sh
> +++ b/tools/find-api-violations.sh
> @@ -6,7 +6,7 @@
>
> # NOTE: This script doesn't look for API violations in function parameters.
>
> -tool_dirs="copy db estimate fs fsck fsr growfs io mdrestore mkfs quota repair rtcp"
> +tool_dirs="copy db estimate fsck fsr growfs io logprint mdrestore mkfs quota repair rtcp"
>
> # Calls to xfs_* functions in libxfs/*.c without the libxfs_ prefix
> find_possible_api_calls() {
>
Looks good to me,
Reviewed-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
--
chandan
prev parent reply other threads:[~2017-01-25 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 5:28 [PATCH v2] tools/find-api-violations: fix missing dirs in the directory list Darrick J. Wong
2017-01-25 5:41 ` Chandan Rajendra [this message]
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=2357002.pCcJ9JlUn9@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).