<linuxppc-dev@lists.ozlabs.org>,oprofile-l...@lists.sf.net,linux-s390 <linux-s...@vger.kernel.org>,sparclinux <sparcli...@vger.kernel.org> From: h...@zytor.com Message-ID: <41625f06-d755-4c82-86df-a9415feee...@zytor.com>
On January 7, 2020 12:08:31 AM PST, Arnd Bergmann <a...@arndb.de> wrote: >On Tue, Jan 7, 2020 at 3:05 AM Michael Ellerman <m...@ellerman.id.au> >wrote: >> Arnd Bergmann <a...@arndb.de> writes: >> > + >> > +static inline compat_uptr_t ptr_to_compat(void __user *uptr) >> > +{ >> > + return (u32)(unsigned long)uptr; >> > +} >> >> Is there a reason we cast to u32 directly instead of using >compat_uptr_t? > >Probably Al found this to be more explicit at the time when he >introduced >it on all the architectures in 2005. I just moved it here and kept the >definition. > > Arnd Did compat_uptr_t exist back then? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.