From: Joe Perches <joe@perches.com>
To: Peter Zijlstra <peterz@infradead.org>,
Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"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 05:01:37 -0700 [thread overview]
Message-ID: <a8677d8c351e4cb49907f9a8addcc261d810655a.camel@perches.com> (raw)
In-Reply-To: <20180412115022.GL4043@hirez.programming.kicks-ass.net>
On Thu, 2018-04-12 at 13:50 +0200, Peter Zijlstra wrote:
> On Thu, Apr 12, 2018 at 11:35:21AM +0200, Andrea Parri wrote:
> > 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,
> > ...)
>
> Yes:
>
> https://lkml.kernel.org/r/$MSGID
>
> that has the added benefit that it immediately includes the msg-id, so
> even if you don't have tubes, you can search for it in your local
> mailboxes.
>
> Also, since we (kernel.org) control the redirection (currently
> marc.info) we can always point it to a life archive.
Message IDs are not useful unless you subscribe and
keep your emails.
It'd be _much_ nicer if vger.kernel.org stored every email
it sent and had a search mechanism available rather than
relying on external systems.
next prev parent reply other threads:[~2018-04-12 12:01 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 [this message]
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
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=a8677d8c351e4cb49907f9a8addcc261d810655a.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=apw@canonical.com \
--cc=fweisbec@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.