[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180412074719.pmcddramzyikppco@gmail.com>
Date: Thu, 12 Apr 2018 09:47:19 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Joe Perches <joe@...ches.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Andy Whitcroft <apw@...onical.com>, yuankuiz@...eaurora.org,
Linux PM <linux-pm@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
paulmck@...ux.vnet.ibm.com, Len Brown <len.brown@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] checkpatch: Add a --strict test for structs with bool
member definitions
* Peter Zijlstra <peterz@...radead.org> wrote:
> I still have room in my /dev/null mailbox for pure checkpatch patches.
>
> > (ooh, https://lkml.org/lkml/2017/11/21/384 is working this morning)
>
> Yes, we really should not use lkml.org for references. Sadly google
> displays it very prominently when you search for something.
lkml.org is nice in emails that have a short expected life time and relevance -
but it probably shouldn't be used for permanent references such as kernel
messages, code comments and Git log entries.
Thanks,
Ingo
Powered by blists - more mailing lists