From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Will Deacon <will@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] kernel.h: Drop unneeded <linux/kernel.h> inclusion from other headers
Date: Fri, 30 Oct 2020 13:06:06 +0200 [thread overview]
Message-ID: <20201030110606.GN4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201030083356.GC32163@willie-the-truck>
On Fri, Oct 30, 2020 at 08:33:56AM +0000, Will Deacon wrote:
> On Wed, Oct 28, 2020 at 07:28:26PM +0200, Andy Shevchenko wrote:
> > There is no evidence we need kernel.h inclusion in certain headers.
>
> Did you run some tools to determine this or is it just a hunch?
I read files manually. So, closer to the latter.
Also I rely on 0day and other CIs that didn't show anything for a long time.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-10-30 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 17:28 [PATCH v1] kernel.h: Drop unneeded <linux/kernel.h> inclusion from other headers Andy Shevchenko
2020-10-30 8:33 ` Will Deacon
2020-10-30 11:06 ` Andy Shevchenko [this message]
2020-12-28 21:37 ` Andy Shevchenko
2021-01-12 14:08 ` Will Deacon
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=20201030110606.GN4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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