Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <1655458375-30478-1-git-send-email-u0084500@gmail.com>
 <1655458375-30478-3-git-send-email-u0084500@gmail.com> <CAHp75VfEQ6tu4-NQKwA+63Ae5busUwV+ZRqD6BtbUA+EkCZnWw@mail.gmail.com>
 <CADiBU3-wO0-0c9y-GpE15ra2AqkAG-ftqTh+hCvYEY-TojZ-pg@mail.gmail.com>
In-Reply-To: <CADiBU3-wO0-0c9y-GpE15ra2AqkAG-ftqTh+hCvYEY-TojZ-pg@mail.gmail.com>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Sun, 19 Jun 2022 12:38:17 +0200
Message-ID: <CAHp75VeBdgbyDQXEYb9ZZdi3AU=vPw6aKGWbNLnuA_QoN4LE4A@mail.gmail.com>
Subject: Re: [PATCH 2/2] iio: adc: Add rtq6056 support
To:     ChiYuan Huang <u0084500@gmail.com>
Cc:     Jonathan Cameron <jic23@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Lars-Peter Clausen <lars@metafoo.de>,
        cy_huang <cy_huang@richtek.com>,
        linux-iio <linux-iio@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        devicetree <devicetree@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, Jun 18, 2022 at 5:16 PM ChiYuan Huang <u0084500@gmail.com> wrote:
> Andy Shevchenko <andy.shevchenko@gmail.com> =E6=96=BC 2022=E5=B9=B46=E6=
=9C=8818=E6=97=A5 =E9=80=B1=E5=85=AD =E5=87=8C=E6=99=A81:08=E5=AF=AB=E9=81=
=93=EF=BC=9A
> > On Fri, Jun 17, 2022 at 11:37 AM cy_huang <u0084500@gmail.com> wrote:

...

> > > +KernelVersion: 5.18.2
> >
> > Wrong version, this won't be part of a stable kernel.
> >
> From kernel.org, currently the stable kernel version is 5.18.5.
> Change to 5.18.5?

Nope. You need to use realistic kernel version, and as I said it can't
be a stable one.

...

> > But for sure you missed

> >   types.h
> >
> Ack in next. But for types.h, i2c.h already include device.h.
> And device.h already include types.h.
> Is it still needed to declare explicitly for types.h??

Yes. You have to include all headers you are a direct user of, except
the ones that are guaranteed to be included by others. The types.h is
not guaranteed to be included by listed above.

...

> > > +       struct device *dev;
> > > +       struct regmap *regmap;
> >
> > Swapping these two might give less code in the generated binary. Have
> > you run bloat-o-meter?
> >
> I never know about this tool.
> I'll check it before I submit the next revision.
> Thanks for the reminding.
>
> But from Jonathan's reply, I may remove 'struct regmap *regmap'.
> If all function need the 'regmap', a local variable 'regmap' need to
> be declared.
> To use struct regmap *regmap =3D dev_get_regmap(dev, NULL) is more effect=
ive.

It's fine, but you may experiment with bloat-o-meter even in that case
out of curiosity.

--=20
With Best Regards,
Andy Shevchenko