Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp4303919pxb; Tue, 2 Mar 2021 11:32:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJwobjE4/zwW5acM3LV5L1bXZWPT96DyjtFXGiqZOlIb8vmoGqdoCcEMVN/adstAAjKKuXYq X-Received: by 2002:a05:6402:17d6:: with SMTP id s22mr21832364edy.232.1614713552274; Tue, 02 Mar 2021 11:32:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614713552; cv=none; d=google.com; s=arc-20160816; b=vsvsZch6Zo5i8v8hTs76HBwNtGHhiqivbvKtJIEiPb4fixeVIgFF6YmjV2vjQctA1R 5ymdmPYGhU6KmySxqimcTYABTVHfOw/keZsrLUzUxo3/UZcz8R9LqqDRJ02yVnjybOgZ rga61qb5SduiV7rdXk6PQU8QA57i9CGhwUbxve9UapmCrpOUQw91QmBDJ/nQJIzrdsIV tNrkE+Xblmc88HzpnbFtJ0q0S0jEx9MoWkRp4BBgsTCpF5Xdm7kqpliUCo4GnwcMNW53 39oBOEqoZomKTyACT1O8wza84AK8q8cdQQ6dRF3wqcPJCeLTB1SQDk2GLXcnx3RhI5Q+ 7N2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=hYs+lGCkT8EgiUCUlbwQTa5H0J9ZzYSxb7M9FOKBgsw=; b=Jtx0Cord60D7Pyos0/JPogAAef5yXijPmuaQWHYlreFjT2pJ6+/65NO5f8YP4Tf9Ds KRdcyzRXeaH5Xho/7/3cJBVaQK2ScUEC5wmfAQ3Lw7wlgD85m6fFENU1981XKajqAVU9 I5XD0qw84OhgI2HN7p7lyBiBNOCQBB61PTP5fSwGoazl4bHT74yybcProEymrdW3WxnT rGeDxjz9joG+GVOl9Op1exFMAm8tW/cQmyUZPafw6mm4GMPxcG5NgnQ03LKxcCFsTyZe /wGJXKmbLvtBn1DUzgOG610e9/Zft4e2wjAe2Dma2HRA2yAwabd6UJcNVLpMKHaK5FpW 5cig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=sNq9+65I; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cw21si4440253edb.344.2021.03.02.11.32.08; Tue, 02 Mar 2021 11:32:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=sNq9+65I; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349260AbhCBG6F (ORCPT + 99 others); Tue, 2 Mar 2021 01:58:05 -0500 Received: from mail.kernel.org ([198.145.29.99]:58758 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344576AbhCBF2f (ORCPT ); Tue, 2 Mar 2021 00:28:35 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6321560241; Tue, 2 Mar 2021 05:27:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614662863; bh=5F27m4NsFLCUr7CLSJiPMlsnMXQ+sltkofLgIHPnvGk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sNq9+65I1HXIDlREZBMnYg0SwjfK3umjU/oEuXmJs9hYOtNenvsnkGQhqdAarWTUE jONksSscb8Hoc6fMza0R+IqX+3Oq3Qeb/dJaZa+/VMCaoOPM1CYbWG85cwX2IjQHwu /uwXSKChGR+VIGjEGWv4jSDXc1o0NQCkv6+Pde7Q= Date: Tue, 2 Mar 2021 06:27:39 +0100 From: "gregkh@linuxfoundation.org" To: "Nguyen, Anthony L" Cc: "Brandeburg, Jesse" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "intel-wired-lan@lists.osuosl.org" , "davem@davemloft.net" , "kuba@kernel.org" Subject: Re: [PATCH] e1000e: use proper #include guard name in hw.h Message-ID: References: <20210227095858.604463-1-gregkh@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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