linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 31 Jan 2018 14:48:56 -0800
From:   Joe Perches <joe@...ches.com>
To:     "Tobin C. Harding" <me@...in.cc>
Cc:     linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: checkpatch changes for 4.16

On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote:
> 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

Personally, I think you could let Andrew Morton pick them
up as very few patches for checkpatch go in any other way.

What patches are you submitting again?

Is it just

commit 7b1924a1d930 ("vsprintf: add printk specifier %px")

or is there something else?