linux-kernel - Re: [PATCH 1/8] arm: Convert pr_warning to pr

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]

Message-ID: <1410898135.16519.14.camel@joe-AO725>
Date:	Tue, 16 Sep 2014 13:08:55 -0700
From:	Joe Perches <joe@...ches.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Will Deacon <will.deacon@....com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/8] arm: Convert pr_warning to pr_warn

On Tue, 2014-09-16 at 20:57 +0100, Russell King - ARM Linux wrote:
> 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 patches@....linux.org.uk 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.

I received your patchbot's reply about 15 minutes
before you sent this.

I suggest you might move one year to patchwork
(ie: https://patchwork.kernel.org/project/linux-arm-kernel/list/)
and adapt that as necessary, but whatever works
for you.

btw:

patches@....linux.org.uk is not documented at all
in the kernel sources.  You could fix that if you
want other people to know what you do.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/