From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
syzbot <syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com>,
acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, bp@alien8.de,
eranian@google.com, hpa@zytor.com, jolsa@kernel.org,
jolsa@redhat.com, linux-kernel@vger.kernel.org, mingo@kernel.org,
mingo@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, torvalds@linux-foundation.org,
x86@kernel.org
Subject: Re: WARNING in perf_reg_value
Date: Thu, 20 Jun 2019 14:13:16 +0200 [thread overview]
Message-ID: <20190620121316.GV3436@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <8ec677d7-f891-1c8b-33bd-16506974fafb@linux.intel.com>
On Wed, Jun 19, 2019 at 05:15:32PM -0400, Liang, Kan wrote:
> Here are the patches posted.
> https://lkml.org/lkml/2019/5/28/1022
How many times do I have to tell that lkml.org links are frigging
useless?
Now I have to copy/paste them into a browser, pray the site works today,
and then copy paste the subject back into my mua and hopefully find the
thread.
If you'd used the canonical form, I'd instantly have a msgid and I
could've search for that directly, without having to have to touch a
browser or hope the interweb actually works.
next prev parent reply other threads:[~2019-06-20 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 19:47 WARNING in perf_reg_value syzbot
2019-06-19 20:07 ` Vince Weaver
2019-06-19 21:15 ` Liang, Kan
2019-06-20 12:13 ` Peter Zijlstra [this message]
2019-12-08 5:03 ` syzbot
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=20190620121316.GV3436@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
--cc=x86@kernel.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