From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Krzysztof Wilczynski <kw@linux.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unicode: Move static keyword to the front of declarations
Date: Tue, 03 Sep 2019 15:52:01 -0400 [thread overview]
Message-ID: <85blw1gntq.fsf@collabora.com> (raw)
In-Reply-To: <20190830131349.14074-1-kw@linux.com> (Krzysztof Wilczynski's message of "Fri, 30 Aug 2019 15:13:49 +0200")
Krzysztof Wilczynski <kw@linux.com> writes:
> Move the static keyword to the front of declarations of nfdi_test_data
> and nfdicf_test_data, and resolve the following compiler warnings that
> can be seen when building with warnings enabled (W=1):
>
> fs/unicode/utf8-selftest.c:38:1: warning:
> ‘static’ is not at beginning of declaration [-Wold-style-declaration]
>
> fs/unicode/utf8-selftest.c:92:1: warning:
> ‘static’ is not at beginning of declaration [-Wold-style-declaration]
>
Applied.
Thanks,
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2019-09-03 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 13:13 [PATCH] unicode: Move static keyword to the front of declarations Krzysztof Wilczynski
2019-09-03 19:52 ` Gabriel Krisman Bertazi [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=85blw1gntq.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=kw@linux.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).