[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vez0fvWWATcX6ofFqREGa64NbAh0ftb=G4WtyvPUvG8VQ@mail.gmail.com>
Date: Wed, 24 Jun 2020 15:49:23 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Petr Mladek <pmladek@...e.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] lockdep: Move list.h inclusion into lockdep.h
On Wed, Jun 24, 2020 at 3:43 PM Herbert Xu <herbert@...dor.apana.org.au> wrote:
> On Tue, Jun 23, 2020 at 04:28:58PM +0200, Petr Mladek wrote:
...
> > -#include <linux/kernel.h>
> > +#include <linux/compiler.h>
>
> Unfortunately this doesn't work because list.h actually does need
> kernel.h for container_of.
>
> However, we can easily fix the loop another way by removing list.h
> from lockdep.h as it doesn't actually use any list macros/functions
> but only the list type which is now in linux/types.h.
>
> We could either fold this into the lockdep_types patch, or fold it
> into the printk patch, or just leave it as a standalone patch.
> What do you guys think?
Does lockdep_types include types? Then we are fine and it is the way to go.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists