linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] e1000e: use proper #include guard name in hw.h
@ 2021-02-27  9:58 Greg Kroah-Hartman
  2021-03-02  1:37 ` Nguyen, Anthony L
  0 siblings, 1 reply; 3+ messages in thread
From: Greg Kroah-Hartman @ 2021-02-27  9:58 UTC (permalink / raw)
  To: jesse.brandeburg, anthony.l.nguyen
  Cc: netdev, linux-kernel, Greg Kroah-Hartman, David S. Miller,
	Jakub Kicinski, intel-wired-lan

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.

This resolves some static analyzer warnings, like the one found by the
"lgtm.com" tool.

Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: intel-wired-lan@lists.osuosl.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 drivers/net/ethernet/intel/e1000e/hw.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/intel/e1000e/hw.h b/drivers/net/ethernet/intel/e1000e/hw.h
index 69a2329ea463..f7954cadd979 100644
--- a/drivers/net/ethernet/intel/e1000e/hw.h
+++ b/drivers/net/ethernet/intel/e1000e/hw.h
@@ -1,8 +1,8 @@
 /* SPDX-License-Identifier: GPL-2.0 */
 /* Copyright(c) 1999 - 2018 Intel Corporation. */
 
-#ifndef _E1000_HW_H_
-#define _E1000_HW_H_
+#ifndef _E1000E_HW_H_
+#define _E1000E_HW_H_
 
 #include "regs.h"
 #include "defines.h"
-- 
2.30.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] e1000e: use proper #include guard name in hw.h
  2021-02-27  9:58 [PATCH] e1000e: use proper #include guard name in hw.h Greg Kroah-Hartman
@ 2021-03-02  1:37 ` Nguyen, Anthony L
  2021-03-02  5:27   ` gregkh
  0 siblings, 1 reply; 3+ messages in thread
From: Nguyen, Anthony L @ 2021-03-02  1:37 UTC (permalink / raw)
  To: Brandeburg, Jesse, gregkh
  Cc: netdev, linux-kernel, intel-wired-lan, davem, kuba

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].

> This resolves some static analyzer warnings, like the one found by
> the
> "lgtm.com" tool.
> 
> Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Cc: Tony Nguyen <anthony.l.nguyen@intel.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: intel-wired-lan@lists.osuosl.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

[1] https://patchwork.ozlabs.org/project/intel-wired-
lan/patch/20210222040005.20126-1-tseewald@gmail.com/

Thanks,
Tony

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] e1000e: use proper #include guard name in hw.h
  2021-03-02  1:37 ` Nguyen, Anthony L
@ 2021-03-02  5:27   ` gregkh
  0 siblings, 0 replies; 3+ messages in thread
From: gregkh @ 2021-03-02  5:27 UTC (permalink / raw)
  To: Nguyen, Anthony L
  Cc: Brandeburg, Jesse, netdev, linux-kernel, intel-wired-lan, davem, kuba

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-03-02  8:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-27  9:58 [PATCH] e1000e: use proper #include guard name in hw.h Greg Kroah-Hartman
2021-03-02  1:37 ` Nguyen, Anthony L
2021-03-02  5:27   ` gregkh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).