From: Julien Grall <julien.grall@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
Ian Campbell <Ian.Campbell@citrix.com>,
tim@xen.org
Subject: Re: [PATCH 0/6] xen/arm: Move in/out code to/from init section
Date: Mon, 02 Feb 2015 13:34:36 +0000 [thread overview]
Message-ID: <54CF7CEC.6010801@linaro.org> (raw)
In-Reply-To: <54CF85DA020000780005BF0F@mail.emea.novell.com>
On 02/02/15 13:12, Jan Beulich wrote:
> This example in particular makes clear that looking at just the
> declaration is insufficient in certain cases.Whoever is looking
> for specific properties of a functions needs to know which ones
> (s)he cares about, and then look in the appropriate place.
__init is common attribute that should be looking by anyone calling a
function. You can't guess about it.
> Unless a rule gets put in place overriding my personal opinion on
this, I'm
> not going to ack or otherwise accept needless code duplication.
It may be needless for the compiler but not for some of the developers.
> If the ARM maintainers feel differently, so be it.
If you look a the ARM headers (asm-arm) we use __init on the prototype.
But x86 and common code is not using it.
The point of this discussion is there is no written rules... It happened
because an x86 maintainer shout about inconsistency on the ARM headers
on my first patch.
If this is going to be the standard on every headers, this should be
written somewhere and not letting the developer guess how the maintainer
will feel about it.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-02-02 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:20 [PATCH 0/6] xen/arm: Move in/out code to/from init section Julien Grall
2015-01-16 16:20 ` [PATCH 1/6] arm/setup: Add missing __init to add_boot_module Julien Grall
2015-01-16 16:28 ` Andrew Cooper
2015-01-16 16:33 ` Julien Grall
2015-01-16 16:20 ` [PATCH 2/6] xen/arm: domain_build: Move all DOM0 building code in init section Julien Grall
2015-01-16 16:20 ` [PATCH 3/6] xen/arm: kernel: Move kernel loading " Julien Grall
2015-01-16 17:33 ` Vitaly Kuznetsov
2015-01-16 17:49 ` Julien Grall
2015-01-19 10:31 ` Ian Campbell
2015-01-16 16:20 ` [PATCH 4/6] xen/arm: device: Move device_type " Julien Grall
2015-01-16 16:20 ` [PATCH 5/6] xen/arm: platforms: Move init_time and specific_mapping " Julien Grall
2015-01-16 16:20 ` [PATCH 6/6] xen/arm: SMP: Move out of the init section the code to bring up a CPU Julien Grall
2015-01-29 18:32 ` [PATCH 0/6] xen/arm: Move in/out code to/from init section Julien Grall
2015-01-30 11:30 ` Ian Campbell
2015-01-30 11:33 ` Julien Grall
2015-02-02 10:58 ` Ian Campbell
2015-02-02 11:15 ` Jan Beulich
2015-02-02 12:52 ` Julien Grall
2015-02-02 13:12 ` Jan Beulich
2015-02-02 13:34 ` Julien Grall [this message]
2015-02-02 12:48 ` Julien Grall
2015-02-02 13:03 ` Ian Campbell
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=54CF7CEC.6010801@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.