From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Anshul Dalal" <anshulusr@gmail.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Yassine Oudjana" <y.oudjana@protonmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Support Opensource" <support.opensource@diasemi.com>,
"Nick Dyer" <nick@shmanahar.org>,
"Hans de Goede" <hansg@kernel.org>,
"Job Noorman" <job@noorman.info>,
"Mika Penttilä" <mpenttil@redhat.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Kees Cook" <kees@kernel.org>,
"bui duc phuc" <phucduc.bui@gmail.com>,
"Thorsten Blum" <thorsten.blum@linux.dev>,
"Yauhen Kharuzhy" <jekhor@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Marco Crivellari" <marco.crivellari@suse.com>,
"Minseong Kim" <ii4gsp@gmail.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Oleh Kuzhylnyi" <kuzhylol@gmail.com>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Josua Mayer" <josua@solid-run.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Jeff LaBundy" <jeff@labundy.com>,
"Javier Carrasco" <javier.carrasco@wolfvision.net>,
"David Heidelberg" <david@ixit.cz>,
"Petr Hodina" <petr.hodina@protonmail.com>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"Johannes Kirchmair" <johannes.kirchmair@skidata.com>,
"Xichao Zhao" <zhao.xichao@vivo.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
platform-driver-x86@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v1] Input: Use named initializers for arrays of i2c_device_data
Date: Mon, 18 May 2026 09:56:02 +0200 [thread overview]
Message-ID: <agrFDLaPu1nnLIN4@monoceros> (raw)
In-Reply-To: <agrAG3cLjEAPV90B@ashevche-desk.local>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Mon, May 18, 2026 at 10:30:35AM +0300, Andy Shevchenko wrote:
> On Mon, May 18, 2026 at 09:24:35AM +0200, Geert Uytterhoeven wrote:
> > Hi Uwe,
> >
> > On Fri, 15 May 2026 at 18:48, Uwe Kleine-König (The Capable Hub)
> > <u.kleine-koenig@baylibre.com> wrote:
> > > My additional motivation for this effort is CHERI[1]. This is a hardware
> >
> > Nice!
> >
> > > extension that uses 128 bit pointers but unsigned long is still 64 bit.
> > > So with CHERI you cannot store pointers in unsigned long variables.
> >
> > Good luck fixing all implicit assumptions about this in the kernel!
> > Also, good luck convincing people to use uintptr_t instead ;-)
> >
> > https://lore.kernel.org/all/CAHk-=wj2OHy-5e+srG1fy+ZU00TmZ1NFp6kFLbVLMXHe7A1d-g@mail.gmail.com
>
> Yeah, I believe Linus will have a strong opinion about all this CHERI stuff :-)
> But let see, it might be surprising turn around.
Yeah, it's not yet the time to start that discussion, I want to have the
patch stack in a better state before that.
I think the strongest argument will be that
"unsigned long" [...] is an integer type large enough to hold a
pointer.
just isn't true for CHERI.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-18 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:48 [PATCH v1] Input: Use named initializers for arrays of i2c_device_data Uwe Kleine-König (The Capable Hub)
2026-05-15 16:53 ` sashiko-bot
2026-05-18 7:24 ` Geert Uytterhoeven
2026-05-18 7:30 ` Andy Shevchenko
2026-05-18 7:56 ` Uwe Kleine-König (The Capable Hub) [this message]
2026-05-30 5:56 ` Dmitry Torokhov
2026-05-30 12:02 ` Uwe Kleine-König (The Capable Hub)
2026-05-31 5:13 ` Dmitry Torokhov
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=agrFDLaPu1nnLIN4@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshulusr@gmail.com \
--cc=clamor95@gmail.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=david@ixit.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=hansg@kernel.org \
--cc=ii4gsp@gmail.com \
--cc=javier.carrasco@wolfvision.net \
--cc=jeff@labundy.com \
--cc=jekhor@gmail.com \
--cc=job@noorman.info \
--cc=johannes.kirchmair@skidata.com \
--cc=josua@solid-run.com \
--cc=kees@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuzhylol@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=m.tretter@pengutronix.de \
--cc=marco.crivellari@suse.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.hennerich@analog.com \
--cc=mingo@kernel.org \
--cc=mpenttil@redhat.com \
--cc=nick@shmanahar.org \
--cc=nicolas.ferre@microchip.com \
--cc=petr.hodina@protonmail.com \
--cc=phucduc.bui@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=support.opensource@diasemi.com \
--cc=tglx@kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=y.oudjana@protonmail.com \
--cc=zhao.xichao@vivo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.