Received-SPF: pass (google.com: domain of linux-kernel+bounces-76153-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <ffec7c7b8eb86f573e420e0582075ba1e75d0e54.camel@perches.com>
Subject: Re: [PATCH 2/2] checkpatch: Don't check for unified diff format in
 git sendemail headers
From: Joe Perches <joe@perches.com>
To: Saravana Kannan <saravanak@google.com>, Andy Whitcroft
 <apw@canonical.com>,  Dwaipayan Ray <dwaipayanray1@gmail.com>, Lukas
 Bulwahn <lukas.bulwahn@gmail.com>
Cc: kernel-team@android.com, linux-kernel@vger.kernel.org
Date: Thu, 22 Feb 2024 00:54:51 -0800
In-Reply-To: <20240222051539.3001988-4-saravanak@google.com>
References: <20240222051539.3001988-3-saravanak@google.com>
	 <20240222051539.3001988-4-saravanak@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
Precedence: bulk
MIME-Version: 1.0

On Wed, 2024-02-21 at 21:15 -0800, Saravana Kannan wrote:
> When checkpatch is used as a git sendemail-validate hook, it's also passe=
d
> in the email header for sanity check.

Why?

If so, why not use a front-end script to stop/remove
the file from being scanned by checkpatch?

> These headers are, as expected, not
> in unified diff format. So, don't complain about unified diff format for
> these header files.