[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aGUTmtdyZEi8yMnT@alpha.franken.de>
Date: Wed, 2 Jul 2025 13:10:18 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH v1 1/1] firmware/nvram: bcm47xx: Don't use "proxy" headers
On Mon, Jun 30, 2025 at 12:03:46PM -0700, Florian Fainelli wrote:
> On 6/26/25 10:59, Andy Shevchenko wrote:
> > Update header inclusions to follow IWYU (Include What You Use)
> > principle.
> >
> > Note that kernel.h is discouraged to be included as it's written
> > at the top of that file.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>
> Reviewed-by: Florian Fainelli <florian.fainelli@...adcom.com>
>
> Thomas, can you pick this up? Thanks!
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists