From: Eric Auger <eric.auger@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: thomas.lendacky@amd.com, eric.auger@st.com,
Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Baptiste Reynal <b.reynal@virtualopensystems.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [RESEND RFC 5/6] hw/arm/sysbus-fdt: helpers for clock node generation
Date: Thu, 17 Dec 2015 16:25:53 +0100 [thread overview]
Message-ID: <5672D401.2040000@linaro.org> (raw)
In-Reply-To: <87vb7xf6r6.fsf@linaro.org>
Hi Alex,
On 12/17/2015 04:13 PM, Alex Bennée wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On 17 December 2015 at 13:28, Alex Bennée <alex.bennee@linaro.org> wrote:
>>> Usually I would expect to see a pre-declaration of a function at the
>>> head of the file and only if it is used before the actual definition of
>>> the function. It doesn't make sense to pre-declare right before the
>>> actual function definition itself.
>>>
>>> I'm surprised to hear the compiler complained, especially as nothing was
>>> calling this function in this patch.
>>
>> The compiler complains if it sees a function which is not static
>> and for which it hasn't previously seen a prototype, because
>> generally this means that either (a) the function is file-local
>> only and should have been declared static or (b) the function is
>> not file-local but you forgot to put a prototype in a header so
>> that other files can call it. (This is -Wmissing-prototypes.)
>
>
> Ahh I see now. I guess if its declared static in this patch and not
> used its going to complain about an unused function as well? Maybe that
> suggests the patch should just be merged with patch where it is actually
> used?
my fear is that it becomes too big for review then. I suggest we wait
for other comments and I will follow the consensus if any. I just wanted
to emphasize I did not ignore your comment but I just don't know how to
handle it at best ;-)
Thanks for your time!
Regards
Eric
>
>>
>> thanks
>> -- PMM
>
>
> --
> Alex Bennée
>
next prev parent reply other threads:[~2015-12-17 15:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 15:22 [Qemu-devel] [RESEND RFC 0/6] AMD XGBE KVM platform passthrough Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 1/6] hw/vfio/platform: amd-xgbe device Eric Auger
2015-11-25 14:35 ` Alex Bennée
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 2/6] device_tree: introduce load_device_tree_from_sysfs Eric Auger
2015-11-25 15:38 ` Alex Bennée
2015-11-26 10:57 ` Thomas Huth
2015-12-03 15:19 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 3/6] device_tree: introduce qemu_fdt_node_path Eric Auger
2015-11-26 12:06 ` Alex Bennée
2015-12-03 15:44 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 4/6] device_tree: introduce qemu_fdt_getprop_optional Eric Auger
2015-11-26 13:13 ` Alex Bennée
2015-11-27 19:38 ` Peter Crosthwaite
2015-12-03 15:48 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 5/6] hw/arm/sysbus-fdt: helpers for clock node generation Eric Auger
2015-11-26 16:06 ` Alex Bennée
2015-12-17 9:26 ` Eric Auger
2015-12-17 13:28 ` Alex Bennée
2015-12-17 13:44 ` Peter Maydell
2015-12-17 15:13 ` Alex Bennée
2015-12-17 15:25 ` Eric Auger [this message]
2015-12-17 15:56 ` Alex Bennée
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 6/6] hw/arm/sysbus-fdt: enable amd-xgbe dynamic instantiation Eric Auger
2015-11-26 17:14 ` Alex Bennée
2015-12-03 16:17 ` Eric Auger
2015-11-19 23:44 ` [Qemu-devel] [RESEND RFC 0/6] AMD XGBE KVM platform passthrough Alex Williamson
2015-11-20 15:10 ` Eric Auger
2015-11-25 10:29 ` Christoffer Dall
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=5672D401.2040000@linaro.org \
--to=eric.auger@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@st.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.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).