From: Ingo Molnar <mingo@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"
Date: Thu, 28 Dec 2017 12:59:55 +0100 [thread overview]
Message-ID: <20171228115955.3rkmzf4gi47hpt63@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1712281221540.2220@hadrien>
* Julia Lawall <julia.lawall@lip6.fr> wrote:
> > So the type is the following, in include/linux/mod_devicetable.h:
> >
> > struct x86_cpu_id {
> > __u16 vendor;
> > __u16 family;
> > __u16 model;
> > __u16 feature; /* bit index */
> > kernel_ulong_t driver_data;
> > };
> >
> > Is there a syntactic method that would allow the conversion to kernel_ulong_t, but
> > would preserve any const-ness?
> >
> > Barring that, maybe we could convert driver_data to 'void *', fix up all users,
> > and not force the type - this would allow the preservation of the const attribute,
> > I think.
> >
> > BTW., a quick grep suggests similar type casting patterns here:
> >
> > arch/x86/platform/intel-mid/pwr.c: { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_PENWELL), (kernel_ulong_t)&pnw_info },
> > arch/x86/platform/intel-mid/pwr.c: { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_TANGIER), (kernel_ulong_t)&tng_info },
>
> Would it be acceptable to move the cast out of the macro to the place
> where the variable is referenced? It wouldn't help with the compiler, but
> it would be slightly easier for the human to check.
It would really be preferably to not stand in the way of the compiler here.
AFACS void * should solve the problem, and it's a kernel_ulong_t equivalent in
terms of with, right?
So let's try and solve this for real. Forcing humans to discover such things is
always a fragile concept.
Thanks,
Ingo
next prev parent reply other threads:[~2017-12-28 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 10:08 [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const" Andy Shevchenko
2017-12-28 10:28 ` Ingo Molnar
2017-12-28 10:34 ` Julia Lawall
2017-12-28 11:12 ` Ingo Molnar
2017-12-28 11:23 ` Julia Lawall
2017-12-28 11:59 ` Ingo Molnar [this message]
2017-12-28 12:12 ` Andy Shevchenko
2017-12-28 12:17 ` Ingo Molnar
2017-12-28 12:25 ` Julia Lawall
2017-12-28 12:29 ` Ingo Molnar
2017-12-28 12:37 ` Julia Lawall
2017-12-28 12:53 ` Ingo Molnar
2017-12-28 14:00 ` Julia Lawall
2017-12-28 15:24 ` Ingo Molnar
2017-12-28 15:28 ` Julia Lawall
2017-12-28 21:22 ` Julia Lawall
2018-01-01 15:15 ` Julia Lawall
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=20171228115955.3rkmzf4gi47hpt63@gmail.com \
--to=mingo@kernel.org \
--cc=andi@firstfloor.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhumirks@gmail.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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