linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Richard Purdie" <rpurdie@rpsys.net>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"H Hartley Sweeten" <hartleys@visionengravers.com>,
	"Fabio Estevam" <fabio.estevam@freescale.com>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	kernel@pengutronix.de
Subject: Re: [PATCH] leds: provide helper to register "leds-gpio" devices
Date: Wed, 20 Apr 2011 00:24:20 +0100	[thread overview]
Message-ID: <20110419232420.GA3673@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110419161913.a1c18599.akpm@linux-foundation.org>

On Tue, Apr 19, 2011 at 04:19:13PM -0700, Andrew Morton wrote:
> On Tue, 5 Apr 2011 17:33:39 +0100
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> 
> > On Tue, Apr 05, 2011 at 10:37:35AM +0200, Uwe Kleine-K__nig wrote:
> > > +struct platform_device *__init gpio_led_register_device(
> > > +		const struct gpio_led_platform_data *pdata);
> > 
> > Please don't add __init annotations to declarations.
> 
> Reasons?

It's noise.

> A year or so ago we had to *add* an __init to a declaration, because
> one architecture was generating a short-mode-addressing relative branch
> to the callee, assuming the target was in the same section as the call
> site.  When the linker went to resolve the branch, it discovered that
> the target was in fact in a different section and was too far away to
> be able to use the short-mode addressing.  IIRC, that architecture was
> arm.

I'm not aware of ARM ever requiring that.  If it was, we'd have to add
a heck of a lot of those annotations.  And those annotations don't tell
the compiler that it might be far away.

We _do_ have a problem if someone decides to include a big ramdisk or
initramfs image in the discarded section, which is something I have a
patch kicking around to completely change the vmlinux layout to resolve.
That's taking something of a low priority at the moment though as we've
been turned upside down by Linus...

  reply	other threads:[~2011-04-19 23:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110405073030.GI13963@pengutronix.de>
2011-04-05  8:37 ` [PATCH] leds: provide helper to register "leds-gpio" devices Uwe Kleine-König
2011-04-05 16:13   ` Fabio Estevam
2011-04-05 16:29     ` Fabio Estevam
2011-04-05 18:12       ` H Hartley Sweeten
2011-04-05 16:33   ` Russell King - ARM Linux
2011-04-05 20:24     ` [PATCH v2] " Uwe Kleine-König
2011-04-06 11:45       ` Fabio Estevam
2011-04-06 11:52       ` Richard Purdie
2011-04-06 12:33         ` Uwe Kleine-König
2011-04-06 13:38           ` Richard Purdie
2011-04-11 20:35             ` [PATCH v3] " Uwe Kleine-König
2011-04-12 21:48               ` Russell King - ARM Linux
2011-04-13  6:23                 ` Uwe Kleine-König
2011-05-06 21:03                   ` Richard Purdie
2011-05-09  8:00                     ` Uwe Kleine-König
2011-04-26 15:08               ` Uwe Kleine-König
2011-05-06  8:25                 ` Uwe Kleine-König
2011-05-09 22:02               ` Andrew Morton
2011-05-09 22:17                 ` Russell King - ARM Linux
2011-05-10  6:45                   ` Uwe Kleine-König
2011-05-10  7:31                 ` Uwe Kleine-König
2011-05-10  8:50                   ` [PATCH v4] " Uwe Kleine-König
2011-05-10  8:50                     ` [PATCH] [wip] ARM: imx: register "leds-gpio" device using new helper function Uwe Kleine-König
2011-05-10 22:26                       ` H Hartley Sweeten
2011-05-11  6:22                         ` Uwe Kleine-König
2011-05-10 23:02                       ` H Hartley Sweeten
2011-04-19 23:19     ` [PATCH] leds: provide helper to register "leds-gpio" devices Andrew Morton
2011-04-19 23:24       ` Russell King - ARM Linux [this message]
2011-04-19 23:50         ` Andrew Morton

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=20110419232420.GA3673@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=fabio.estevam@freescale.com \
    --cc=hartleys@visionengravers.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=s.hauer@pengutronix.de \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).