linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Larsson <andreas@gaisler.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, software@gaisler.com
Subject: Re: [PATCH v2] can: sja1000: Make sja1000_of_platform selectable and compilable on SPARC
Date: Fri, 05 Oct 2012 11:01:52 +0200	[thread overview]
Message-ID: <506EA200.1040500@gaisler.com> (raw)
In-Reply-To: <506DA769.6090000@pengutronix.de>

On 10/04/2012 05:12 PM, Marc Kleine-Budde wrote:
> On 10/04/2012 04:42 PM, Marc Kleine-Budde wrote:
>> On 10/04/2012 03:59 PM, Andreas Larsson wrote:
>>> Signed-off-by: Andreas Larsson <andreas@gaisler.com>
>>
>> Looks better. However on sparc and sparc64, I'm seeing this warning.
>>  From my point of view a false positive.
>>
>>> linux/drivers/net/can/sja1000/sja1000_of_platform.c: In function 'sja1000_ofp_remove':
>>> linux/include/linux/ioport.h:165:18: warning: 'res.end' is used uninitialized in this function [-Wuninitialized]
>>> linux/drivers/net/can/sja1000/sja1000_of_platform.c:78:18: note: 'res.end' was declared here
>>> linux/include/linux/ioport.h:165:2: warning: 'res.start' is used uninitialized in this function [-Wuninitialized]
>>> linux/drivers/net/can/sja1000/sja1000_of_platform.c:78:18: note: 'res.start' was declared here
>
> Looking at the preprocessed code, the compiler is right:
>
>> # 30 "/home/frogger/pengutronix/socketcan/linux/include/linux/of_address.h"
>> static inline __attribute__((always_inline)) __attribute__((no_instrument_function)) int of_address_to_resource(struct device_node *dev, int index,
>>        struct resource *r)
>> {
>>   return -22;
>> }
>
> http://lxr.free-electrons.com/source/include/linux/of_address.h#L29
>
> Why is CONFIG_OF_ADDRESS not set in my .config?

In drivers/of/Kconfig, OF_ADDRESS depends on !SPARC as sparc handles a 
bunch of open firmware things differently. There is a sparc-specific 
implementations of of_address_to_resource.

I'll send in a patch changing of_address.h so that 
of_address_to_resource gets declared extern for sparc instead of an 
empty inline function. That should solve the problem as far as I see it.

There is a similar thing with CONFIG_OF_IRQ, of_irq.h and 
irq_of_parse_and_map, but there irq_of_parse_and_map is declared outside 
of #ifdef CONFIG_OF_IRQ because of the sparc specific implementation.

Cheers,
Andreas


  reply	other threads:[~2012-10-05  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 13:13 [PATCH] can: sja1000: Make sja1000_of_platform selectable and compilable on SPARC Andreas Larsson
2012-10-04 12:49 ` Marc Kleine-Budde
2012-10-04 13:43   ` Andreas Larsson
2012-10-04 13:59     ` [PATCH v2] " Andreas Larsson
2012-10-04 14:42       ` Marc Kleine-Budde
2012-10-04 15:12         ` Marc Kleine-Budde
2012-10-05  9:01           ` Andreas Larsson [this message]
2012-10-05  9:05             ` Marc Kleine-Budde
2012-10-05  9:16               ` Andreas Larsson
2012-10-05  9:19                 ` Marc Kleine-Budde
2012-11-12 17:52       ` Andreas Larsson
2012-11-22 11:30         ` Marc Kleine-Budde

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=506EA200.1040500@gaisler.com \
    --to=andreas@gaisler.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=software@gaisler.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).