From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Matthew Wilcox <willy@infradead.org>,
Maximilian Luz <luzmaximilian@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Wolfram Sang <wsa@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sean Young <sean@mess.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Jiri Slaby <jirislaby@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Chaitanya Kulkarni <kch@nvidia.com>,
Ming Lei <ming.lei@redhat.com>, Jilin Yuan <yuanjilin@cdjrlc.com>,
Alan Stern <stern@rowland.harvard.edu>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Won Chung <wonchung@google.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-block@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-i3c@lists.infradead.org,
linux-input@vger.kernel.org, linux-media@vger.kernel.org,
linux-serial@vger.kernel.org, linux-usb@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 3/5] driver core: make struct device_type.uevent() take a const *
Date: Wed, 23 Nov 2022 20:06:20 +0100 [thread overview]
Message-ID: <Y35vLAWWfezPvGSm@kroah.com> (raw)
In-Reply-To: <Y35lt+0jXrOKynL5@ziepe.ca>
On Wed, Nov 23, 2022 at 02:25:59PM -0400, Jason Gunthorpe wrote:
> On Wed, Nov 23, 2022 at 07:10:49PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Nov 23, 2022 at 05:49:36PM +0000, Matthew Wilcox wrote:
> > > On Wed, Nov 23, 2022 at 01:29:56PM -0400, Jason Gunthorpe wrote:
> > > > #define generic_container_of(in_type, in, out_type, out_member) \
> > > > _Generic(in, \
> > > > const in_type *: ((const out_type *)container_of(in, out_type, out_member)), \
> > > > in_type *: ((out_type *)container_of(in, out_type, out_member)) \
> > > > )
> > >
> > > There's a neat trick I found in seqlock.h:
> > >
> > > #define generic_container_of(in_t, in, out_t, m) \
> > > _Generic(*(in), \
> > > const in_t: ((const out_t *)container_of(in, out_t, m)), \
> > > in_t: ((out_t *)container_of(in, out_type, m)) \
> > > )
> > >
> > > and now it fits in 80 columns ;-)
> >
> > Nice trick! Dropping the inline functions is a bit different, let me
> > see if that still gives a sane error if we pass an incorrect type or
> > mess with the const * the wrong way. I'll run some tests tomorrow
> > afternoon...
>
> The errors in some cases are very verbose, but it is somewhat
> understandable - the worst is when _Generic fails to match anything,
> but also at least clang partially expanded container_of and it throws
> other assertions too.
>
> I also wonder if this could just be rolled into the normal
> container_of.
I think we might be able to now, my previous attempts with inline
functions prevented that. I'll beat on that tomorrow...
> in_type would have to be derived like:
>
> in_type = typeof((out_type *)NULL)->out_member)
>
> But I don't know if you can use typeof in a generic type matching expression..
Maybe that is what threw me before, I can't remember. I do know we
tried a number of different attempts, can't recall the failed ones...
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-23 19:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221123122523.1332370-1-gregkh@linuxfoundation.org>
2022-11-23 12:25 ` [PATCH 2/5] driver core: make struct class.devnode() take a const * Greg Kroah-Hartman
2022-11-25 11:55 ` Mauro Carvalho Chehab
2022-11-25 12:40 ` Sumit Semwal
2022-11-23 12:25 ` [PATCH 3/5] driver core: make struct device_type.uevent() " Greg Kroah-Hartman
2022-11-23 12:38 ` Rafael J. Wysocki
2023-01-11 9:51 ` Greg Kroah-Hartman
2022-11-23 13:14 ` Maximilian Luz
2022-11-23 13:34 ` Andy Shevchenko
2022-11-23 13:59 ` Maximilian Luz
2022-11-23 14:52 ` Matthew Wilcox
2022-11-23 15:14 ` Maximilian Luz
2022-11-23 15:37 ` Greg Kroah-Hartman
2022-11-23 15:48 ` Maximilian Luz
2022-11-23 15:52 ` Greg Kroah-Hartman
2022-11-23 16:25 ` Jason Gunthorpe
2022-11-23 17:01 ` Greg Kroah-Hartman
2022-11-23 17:29 ` Jason Gunthorpe
2022-11-23 17:49 ` Matthew Wilcox
2022-11-23 17:55 ` Jason Gunthorpe
2022-11-23 18:00 ` Matthew Wilcox
2022-12-01 18:43 ` Greg Kroah-Hartman
2022-11-23 18:10 ` Greg Kroah-Hartman
2022-11-23 18:25 ` Jason Gunthorpe
2022-11-23 19:06 ` Greg Kroah-Hartman [this message]
2022-11-23 23:24 ` Barnabás Pőcze
2022-11-23 13:56 ` Mika Westerberg
2023-01-11 9:52 ` Greg Kroah-Hartman
2022-11-25 11:56 ` Mauro Carvalho Chehab
2023-01-11 9:52 ` Greg Kroah-Hartman
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=Y35vLAWWfezPvGSm@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=andreas.noever@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=frowand.list@gmail.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=jirislaby@kernel.org \
--cc=kch@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=luzmaximilian@gmail.com \
--cc=markgross@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab@kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ming.lei@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=sean@mess.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=vkoul@kernel.org \
--cc=willy@infradead.org \
--cc=wonchung@google.com \
--cc=wsa@kernel.org \
--cc=yuanjilin@cdjrlc.com \
--cc=yung-chuan.liao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).