From: Kalle Valo <kvalo@codeaurora.org>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andy Whitcroft <apw@canonical.com>,
yuankuiz@codeaurora.org, Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
paulmck@linux.vnet.ibm.com, Len Brown <len.brown@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Add a --strict test for structs with bool member definitions
Date: Thu, 12 Apr 2018 14:52:14 +0300 [thread overview]
Message-ID: <87a7u8iqvl.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20180412093521.GA6427@andrea> (Andrea Parri's message of "Thu, 12 Apr 2018 11:35:21 +0200")
Andrea Parri <andrea.parri@amarulasolutions.com> writes:
> On Thu, Apr 12, 2018 at 09:47:19AM +0200, Ingo Molnar wrote:
>>
>> * Peter Zijlstra <peterz@infradead.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.
>
> 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
prev parent reply other threads:[~2018-04-12 11:52 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 7:33 Subject: [PATCH] [PATCH] time: tick-sched: use bool for tick_stopped yuankuiz
2018-04-10 7:45 ` yuankuiz
2018-04-10 8:51 ` yuankuiz
2018-04-10 8:54 ` yuankuiz
2018-04-10 7:55 ` Subject: [PATCH] " Thomas Gleixner
2018-04-10 8:12 ` yuankuiz
2018-04-10 8:00 ` Rafael J. Wysocki
2018-04-10 8:15 ` yuankuiz
2018-04-10 9:10 ` Thomas Gleixner
2018-04-10 10:07 ` yuankuiz
2018-04-10 11:06 ` Thomas Gleixner
2018-04-10 14:08 ` yuankuiz
2018-04-10 14:49 ` yuankuiz
2018-04-10 23:09 ` yuankuiz
2018-04-10 23:20 ` yuankuiz
2018-04-20 1:47 ` yuankuiz
2018-04-20 6:44 ` yuankuiz
2018-04-20 19:24 ` Joe Perches
2018-04-25 7:01 ` yuankuiz
2018-04-10 11:26 ` Peter Zijlstra
2018-04-10 12:07 ` Thomas Gleixner
2018-04-10 12:26 ` Peter Zijlstra
2018-04-10 12:33 ` Subject: [PATCH] " Peter Zijlstra
2018-04-10 15:14 ` Joe Perches
2018-04-10 16:30 ` Peter Zijlstra
2018-04-10 15:41 ` [PATCH] checkpatch: whinge about bool bitfields Joe Perches
2018-04-10 18:19 ` [PATCH] checkpatch: Add a --strict test for structs with bool member definitions Joe Perches
2018-04-10 21:39 ` Andrew Morton
2018-04-10 21:53 ` Joe Perches
2018-04-10 22:00 ` Andrew Morton
2018-04-11 8:15 ` Peter Zijlstra
2018-04-11 16:29 ` Andrew Morton
2018-04-11 16:51 ` Joe Perches
2018-04-12 6:22 ` Julia Lawall
2018-04-12 6:42 ` Joe Perches
2018-04-12 7:03 ` Julia Lawall
2018-04-12 8:13 ` Peter Zijlstra
2018-04-14 21:19 ` Julia Lawall
2018-04-17 9:07 ` yuankuiz
2018-04-18 18:38 ` Joe Perches
2018-04-19 4:40 ` Julia Lawall
2018-04-19 4:51 ` Joe Perches
2018-04-19 5:16 ` Julia Lawall
2018-04-19 6:48 ` yuankuiz
2018-04-19 10:42 ` yuankuiz
2018-04-20 1:31 ` yuankuiz
2018-04-11 17:00 ` Peter Zijlstra
2018-04-12 7:47 ` Ingo Molnar
2018-04-12 8:11 ` Peter Zijlstra
2018-04-12 9:35 ` Andrea Parri
2018-04-12 11:50 ` Peter Zijlstra
2018-04-12 12:01 ` Joe Perches
2018-04-12 12:08 ` Peter Zijlstra
2018-04-12 12:38 ` Joe Perches
2018-04-12 16:47 ` Andrew Morton
2018-04-12 11:52 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7u8iqvl.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=apw@canonical.com \
--cc=fweisbec@gmail.com \
--cc=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=yuankuiz@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).