lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CANg-bXBwWXaJWv9gMtjYvRBnOaP3E8U1nh5-ScWOoyRayzn7Zw@mail.gmail.com> Date: Wed, 27 Dec 2023 12:09:19 -0700 From: Mark Hasemeyer <markhas@...omium.org> To: Andy Shevchenko <andriy.shevchenko@...el.com> Cc: LKML <linux-kernel@...r.kernel.org>, AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Rob Herring <robh@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, Sudeep Holla <sudeep.holla@....com>, Raul Rangel <rrangel@...omium.org>, Tzung-Bi Shih <tzungbi@...nel.org>, Daniel Scally <djrscally@...il.com>, Frank Rowand <frowand.list@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Len Brown <lenb@...nel.org>, "Rafael J. Wysocki" <rafael@...nel.org>, Rob Herring <robh+dt@...nel.org>, Sakari Ailus <sakari.ailus@...ux.intel.com>, devicetree@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: [PATCH v3 21/24] device property: Modify fwnode irq_get() to use resource > A side note: in all files where you use ioport.h check if you actually included it. > > ... > > > -#include <linux/types.h> > > -#include <linux/list.h> > > #include <linux/bits.h> > > #include <linux/err.h> > > +#include <linux/ioport.h> > > +#include <linux/list.h> > > +#include <linux/types.h> > > Fine, but no. This file is still not using the iopoll.h. > See the forward declarations below? It should be there. > > > struct fwnode_operations; > > struct device; > > ... > > > --- a/include/linux/property.h > > +++ b/include/linux/property.h > > Same comment(s) here. I don't fully follow. Are you suggesting adding an explicit 'struct resource' declaration as opposed to including ioport.h? If so, why? To reduce scope?
Powered by blists - more mailing lists