[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170920163117.GA502@tigerII.localdomain>
Date: Thu, 21 Sep 2017 01:31:17 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Helge Deller <deller@....de>,
David Laight <David.Laight@...LAB.COM>
Cc: 'Sergey Senozhatsky' <sergey.senozhatsky.work@...il.com>,
Fenghua Yu <fenghua.yu@...el.com>,
"Luck, Tony" <tony.luck@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
Petr Mladek <pmladek@...e.com>, Jessica Yu <jeyu@...nel.org>,
"James E . J . Bottomley" <jejb@...isc-linux.org>,
Steven Rostedt <rostedt@...dmis.org>,
Alexei Starovoitov <ast@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate
%pF/%pf printk specifiers
On (09/20/17 12:20), Helge Deller wrote:
[..]
> > I've not looked at the specifics case...
> >
> > Another option is using a struct with a single member and
> > passing it by value.
>
> Actually, we do already have correct structs which could be referenced:
> parisc: struct Elf64_Fdesc
> ia64: struct fdesc
> ppc64: struct ppc64_opd_entry
>
> One could "#define platform_opd_entry" to each of those depending on the platform and use it.
> It might be misleading though, because the pointer which is handed over to
> dereference_function_descriptor() can be such a pointer but isn't necessary.
> I'll leave it up to Sergey to decide.
Hello,
I think I'll keep 'unsigned long' for now.
-ss
Powered by blists - more mailing lists