[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1426183481.2146.80.camel@HansenPartnership.com>
Date: Thu, 12 Mar 2015 14:04:41 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Scott Wood <scottwood@...escale.com>
Cc: trivial@...nel.org, linux-kernel@...r.kernel.org,
linux-parisc@...r.kernel.org
Subject: Re: [PATCH 14/22] parisc: %pF is only for function pointers
On Thu, 2015-03-12 at 11:14 -0500, Scott Wood wrote:
> On Thu, 2015-03-12 at 08:11 -0400, James Bottomley wrote:
> > On Wed, 2015-03-11 at 22:13 -0500, Scott Wood wrote:
> > > Use %pS for actual addresses, otherwise you'll get bad output
> > > on arches like ppc64 where %pF expects a function descriptor. Even on
> > > other architectures, refrain from setting a bad example that people
> > > copy.
> >
> > Are you sure about this? Parisc64 is a function description
> > architecture. There may be a misunderstanding about what
> > __builtin_return_address(0) is supposed to return, but I'm certain the
> > person who added the code thought it returned a function pointer, which
> > on parisc64 would be a descriptor.
>
> I wasn't aware that parisc64 used descriptors, but I don't see how you'd
> get one out of __builtin_return_address(0) since it's not usually a
> function entry point (plus, GCC documents it as returning void *).
I was more thinking that this message is printed for every boot with a
superio chip (which is a lot of our boxes). How come no-one has
complained on parisc64 if it's doing the wrong thing.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists