From: Qian Cai <cai@lca.pw>
To: paulmck@kernel.org
Cc: Andrey Konovalov <andreyknvl@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v3] kcsan: Add option for verbose reporting
Date: Mon, 6 Apr 2020 09:45:44 -0400 [thread overview]
Message-ID: <67156109-7D79-45B7-8C09-E98D25069928@lca.pw> (raw)
In-Reply-To: <20200406133543.GB19865@paulmck-ThinkPad-P72>
> On Apr 6, 2020, at 9:35 AM, Paul E. McKenney <paulmck@kernel.org> wrote:
>
> It goes back in in seven days, after -rc1 is released. The fact that
> it was there last week was a mistake on my part, and I did eventually
> get my hand slapped for it. ;-)
>
> In the meantime, if it would help, I could group the KCSAN commits
> on top of those in -tip to allow you to get them with one "git pull"
> command.
Testing Linux-next for a week without that commit with KCSAN is a torture, so please do that if that is not much work. Otherwise, I could manually cherry-pick the commit myself after fixing all the offsets.
next prev parent reply other threads:[~2020-04-06 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:10 [PATCH v3] kcsan: Add option for verbose reporting Marco Elver
2020-02-22 1:36 ` Paul E. McKenney
2020-02-24 19:16 ` Marco Elver
2020-03-01 18:58 ` Paul E. McKenney
2020-04-06 12:59 ` Qian Cai
2020-04-06 13:35 ` Paul E. McKenney
2020-04-06 13:45 ` Qian Cai [this message]
2020-04-06 19:51 ` Paul E. McKenney
2020-04-06 20:33 ` Qian Cai
2020-04-15 22:42 ` Paul E. McKenney
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=67156109-7D79-45B7-8C09-E98D25069928@lca.pw \
--to=cai@lca.pw \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).