[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf6iN7yEdubKFkf+fXupVTco-toZN=a5+KNXG4Yv6oT3Q@mail.gmail.com>
Date: Wed, 22 Dec 2021 20:52:30 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Liam Beguin <liambeguin@...il.com>
Cc: Peter Rosin <peda@...ntia.se>, Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-iio <linux-iio@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v11 04/15] iio: afe: rescale: expose scale processing function
On Wed, Dec 22, 2021 at 8:20 PM Liam Beguin <liambeguin@...il.com> wrote:
> On Wed, Dec 22, 2021 at 12:21:01PM +0200, Andy Shevchenko wrote:
> > On Wed, Dec 22, 2021 at 5:46 AM Liam Beguin <liambeguin@...il.com> wrote:
...
> > > #include <linux/iio/consumer.h>
> > > #include <linux/iio/iio.h>
> > > +#include <linux/iio/afe/rescale.h>
> >
> > It should go before the consumer.h, no?
>
> I don't mind making the change, but why should it go before consumer.h?
'a' is earlier than 'c' in the alphabet, no?
...
> > And I would rather move the entire IIO group of headers...
>
> I can do that too. Do we have a convention for the ordering of #includes?
> What's usually the rule/guideline for this?
Guidelines suggest sorting without clear instructions. But in IIO and
pin control I suggest people use this kind of grouping.
> > > #include <linux/module.h>
> > > #include <linux/of.h>
> > > #include <linux/of_device.h>
> > > #include <linux/platform_device.h>
> > > #include <linux/property.h>
> >
> > ... somewhere here (with blank line above).
> >
> > > -struct rescale;
...
> > Missed types.h and forward declarations like
> > struct device;
>
> Okay. will add linux/types.h
What about forward declaration?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists