linux-kernel - checkpatch changes for 4.16

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180131214630.GF11433@eros>
Date:   Thu, 1 Feb 2018 08:46:30 +1100
From:   "Tobin C. Harding" <me@...in.cc>
To:     Joe Perches <joe@...ches.com>
Cc:     linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com>
Subject: checkpatch changes for 4.16

Hi Joe,

Can I please bother you with a maintainer question.  I know everyone is
super busy right now, I'm asking for a smidgen of your time instead of
doing it wrong and taking up some of Linus' time since it's merge window
and all that.

I have the checkpatch set queued ready to do a GIT PULL to Linus.  My
concern is that the subject line may not be unique if checkpatch changes
are coming in from various trees this merge window. I have tagged the
pull request with

	checkpatch-4.16-rc1

with the subject line

	[GIT PULL] checkpatch changes for 4.16-rc1

If there are no other changes to checkpatch going in this merge window
then this issue dissolves.  If there are, should I add something to the
subject line to ensure it is unique?

Thanks and sorry for targeting you with this question, I'm sure you have
better things to do also.

	Tobin