From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752437AbeDLLwY (ORCPT ); Thu, 12 Apr 2018 07:52:24 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:45960 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751953AbeDLLwW (ORCPT ); Thu, 12 Apr 2018 07:52:22 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org C608B60290 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=kvalo@codeaurora.org From: Kalle Valo To: Andrea Parri Cc: Ingo Molnar , Peter Zijlstra , Andrew Morton , Joe Perches , "Rafael J. Wysocki" , Andy Whitcroft , yuankuiz@codeaurora.org, Linux PM , "Rafael J. Wysocki" , Frederic Weisbecker , Thomas Gleixner , paulmck@linux.vnet.ibm.com, Len Brown , Linux Kernel Mailing List Subject: Re: [PATCH] checkpatch: Add a --strict test for structs with bool member definitions References: <20180410123305.GF4082@hirez.programming.kicks-ass.net> <95477c93db187bab6da8a8ba7c57836868446179.camel@perches.com> <20180410143950.4b8526073b4e3e34689f68cb@linux-foundation.org> <20180410150011.df9e036f57b5bcac7ac19686@linux-foundation.org> <20180411081502.GJ4082@hirez.programming.kicks-ass.net> <20180411092959.e666ec443e4d3bb6f43901d7@linux-foundation.org> <20180411170049.GR4082@hirez.programming.kicks-ass.net> <20180412074719.pmcddramzyikppco@gmail.com> <20180412093521.GA6427@andrea> Date: Thu, 12 Apr 2018 14:52:14 +0300 In-Reply-To: <20180412093521.GA6427@andrea> (Andrea Parri's message of "Thu, 12 Apr 2018 11:35:21 +0200") Message-ID: <87a7u8iqvl.fsf@purkki.adurom.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrea Parri writes: > On Thu, Apr 12, 2018 at 09:47:19AM +0200, Ingo Molnar wrote: >> >> * Peter Zijlstra 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. > > Is there a better or recommended way to reference posts on LKML in commit > messages? (I do like the idea of linking to previous discussions, results, > ...) I like lkml.kernel.org, for example a link to your message would be: https://lkml.kernel.org/r/20180412093521.GA6427@andrea BTW, I think it would be a good idea to add a hostname to your Message-Id. -- Kalle Valo