[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YD3Myz2psace5IqO@kroah.com>
Date: Tue, 2 Mar 2021 06:27:39 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>
Subject: Re: [PATCH] e1000e: use proper #include guard name in hw.h
On Tue, Mar 02, 2021 at 01:37:59AM +0000, Nguyen, Anthony L wrote:
> On Sat, 2021-02-27 at 10:58 +0100, Greg Kroah-Hartman wrote:
> > The include guard for the e1000e and e1000 hw.h files are the same,
> > so
> > add the proper "E" term to the hw.h file for the e1000e driver.
>
> There's a patch in process that addresses this issue [1].
Thanks, hopefully it gets fixed somehow :)
greg k-h
Powered by blists - more mailing lists