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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Sep 2014 20:57:38 +0100
From:	Russell King - ARM Linux <>
To:	Joe Perches <>
Cc:	Will Deacon <>,
	Peter Zijlstra <>,
	Paul Mackerras <>,
	Ingo Molnar <>,
	Arnaldo Carvalho de Melo <>,
	"" <>
Subject: Re: [PATCH 1/8] arm: Convert pr_warning to pr_warn

On Tue, Sep 16, 2014 at 09:18:01AM -0700, Joe Perches wrote:
> On Tue, 2014-09-16 at 17:07 +0100, Russell King - ARM Linux wrote:
> > any chance you could add a KernelVersion: tag somewhere in the
> > commit message and throw it at so it doesn't
> > get lost?
> There are no commit logs with a KernelVersion: tag
> in all of git history.

Right, that's not it's purpose.

> What do you think a KernelVersion: tag is and what
> would it be used for?

It's for that email address to know which kernel version the patch
was generated against, which is useful information when I come to
apply it.  It gets filtered out from the commit message.  It can go
anywhere, even below the -- line.

If you don't want to cooperate, you will have to rely on my notoriously
bad email skills to scan the mailing list for random patches to apply
some time (maybe days or even weeks) later after you send your message.
Which just won't happen.  It's why I wrote scripts which are some 20
years old to solve my bad email patch handling skills.

FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists