From: Leon Romanovsky <leon@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Add function declaration of simple_dname
Date: Wed, 19 Aug 2020 14:58:21 +0300 [thread overview]
Message-ID: <20200819115821.GV7555@unreal> (raw)
In-Reply-To: <20200819114755.GC17456@casper.infradead.org>
On Wed, Aug 19, 2020 at 12:47:55PM +0100, Matthew Wilcox wrote:
> On Wed, Aug 19, 2020 at 02:40:01PM +0300, Leon Romanovsky wrote:
> > On Wed, Aug 19, 2020 at 12:34:24PM +0100, Matthew Wilcox wrote:
> > > On Wed, Aug 19, 2020 at 11:32:59AM +0300, Leon Romanovsky wrote:
> > > > From: Leon Romanovsky <leonro@nvidia.com>
> > > >
> > > > The simple_dname() is declared in internal header file as extern
> > > > and this generates the following GCC warning.
> > >
> > > The fact that it's declared as extern doesn't matter. You don't need
> > > the change to internal.h at all. The use of 'extern' on a function
> > > declaration is purely decorative:
> > >
> > > 5 If the declaration of an identifier for a function has no
> > > storage-class specifier, its linkage is determined exactly as if it
> > > were declared with the storage-class specifier extern.
> >
> > So why do we need to keep extern keyword if we use intenral.h directly?
>
> We don't. It's just personal preference. I don't use extern keywords
> on function declarations anywhere, but Al does and it's rude to change it.
I didn't have any intention to be rude, just like you, I don't use extern keyword.
I'll resend to make a progress.
Thanks
>
prev parent reply other threads:[~2020-08-19 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 8:32 [PATCH] fs: Add function declaration of simple_dname Leon Romanovsky
2020-08-19 11:34 ` Matthew Wilcox
2020-08-19 11:40 ` Leon Romanovsky
2020-08-19 11:47 ` Matthew Wilcox
2020-08-19 11:58 ` Leon Romanovsky [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=20200819115821.GV7555@unreal \
--to=leon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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