From: Lee Jones <lee.jones@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] mfd: intel-lpss: Move linux/pm.h to the local header
Date: Tue, 12 Feb 2019 08:49:12 +0000 [thread overview]
Message-ID: <20190212084912.GX20638@dell> (raw)
In-Reply-To: <20190208125958.GN9224@smile.fi.intel.com>
On Fri, 08 Feb 2019, Andy Shevchenko wrote:
> On Fri, Feb 01, 2019 at 03:08:17PM +0000, Lee Jones wrote:
> > On Fri, 01 Feb 2019, Andy Shevchenko wrote:
> > > On Fri, Feb 1, 2019 at 11:50 AM Lee Jones <lee.jones@linaro.org> wrote:
> > > > On Thu, 24 Jan 2019, Andy Shevchenko wrote:
> > > >
> > > > > We now using a common macro for PM operations in Intel LPSS driver,
> > > > > and, since that macro relies on the definition and macro from linux/pm.h
> > > > > header file, it's logical to include it directly in intel-lpss.h.
> > > > > Otherwise it's a bit fragile and requires a proper ordering
> > > > > of header inclusion in C files.
> > > >
> > > > I don't agree with this. File which use various headers should
> > > > explicitly include them. Inheriting header files is non-optimal.
> > > >
> > >
> > > intel-lpss.h _is_ using pm.h.
> > > I don't see a contradiction here.
> >
> > Then it should be including in there *also*.
>
> Why?
>
> intel-lpss-*.c are not direct users of this header.
They're not? That's is where the miscommunication lies then.
If a C-file isn't using the offerings of a headerfile, obviously there
is no need for the C-file to include it.
> > My point is that if drivers/mfd/intel-lpss-{acpi,pci}.c use the header
> > file, it should include it explicitly.
>
> They are using it indirectly.
Indirectly is fine.
> As far as I know we don't, for example, include "asm/*.h" to each of our C-file
> because they are in _indirect_ use of.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-02-12 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 18:03 [PATCH v1] mfd: intel-lpss: Move linux/pm.h to the local header Andy Shevchenko
2019-01-29 14:48 ` Mika Westerberg
2019-02-01 9:25 ` Lee Jones
2019-02-01 10:05 ` Andy Shevchenko
2019-02-01 15:08 ` Lee Jones
2019-02-08 12:59 ` Andy Shevchenko
2019-02-12 8:49 ` Lee Jones [this message]
2019-02-12 8:49 ` Lee Jones
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=20190212084912.GX20638@dell \
--to=lee.jones@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@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 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.