[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOAebxtib1o7sUG5KovAuGEWb3YsxPQO1O=m1N696e8sGM9UVQ@mail.gmail.com>
Date: Tue, 14 Nov 2017 22:56:03 -0500
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: Dou Liyang <douly.fnst@...fujitsu.com>
Cc: Steve Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
linux@...linux.org.uk, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, John Stultz <john.stultz@...aro.org>,
sboyd@...eaurora.org, x86@...nel.org, linux-kernel@...r.kernel.org,
mingo@...hat.com, Thomas Gleixner <tglx@...utronix.de>,
hpa@...or.com
Subject: Re: [PATCH v8 2/6] time: sync read_boot_clock64() with persistent clock
> IMO, using the extern keyword on function prototypes in *.h files
> is superfluous, but, It doesn't matter for functionality. *extern*
> is default keywords.
>
> AFAIK, it's a code style problem. In x86 arch, we prefer to
> keep *extern* explicitly, so, let's keep it like before for
> code consistency.
Sounds good, I will restore externs.
Thank you,
Pavel
Powered by blists - more mailing lists