From: "Paul E. McKenney" <paulmck@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org,
elver@google.com, linux-kernel@vger.kernel.org
Subject: Re: Please can I have a stable KCSAN branch for 5.8?
Date: Wed, 6 May 2020 07:36:16 -0700 [thread overview]
Message-ID: <20200506143616.GY2869@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200506132816.GJ8043@willie-the-truck>
On Wed, May 06, 2020 at 02:28:17PM +0100, Will Deacon wrote:
> Hi TIP folks,
>
> I'm looking to rebase my READ_ONCE() series [1] on top of the KCSAN patches
> so that we can get them in for 5.8. However, tip/locking/kcsan seems to be
> missing some bits:
>
> * An update to checkpatch.pl to warn about missing comments for
> data_race():
>
> https://lore.kernel.org/r/20200401101714.44781-1-elver@google.com
For some reason, I thought this was going up some other tree, but I do
not see it in -next. So unless I hear otherwise, I will pull it into
the v5.8 kcsan branch.
> * I'm unable to apply these two patches from Marco that are needed for
> my READ_ONCE() work:
>
> https://lore.kernel.org/lkml/20200424154730.190041-1-elver@google.com/
>
> I think these depend on stuff that has been queued by Paul, and appears
> in linux-next, but to be honest with you I'm quite confused about what
> is queued for 5.8 and what isn't.
This one is queued, but I currently have it in the v5.9 pile (but
tentatively for v5.8). Unless Marco tells me otherwise, I will move it
to the v5.8 branch, which will be part of my pull request next week.
> What's the best base for me to use?
The -next tree has the latter, but not yet the former.
Hopefully we can get this straightened out, and please accept my apologies
for the hassle!
Thanx, Paul
> Cheers,
>
> Will
>
> [1] https://lore.kernel.org/r/20200421151537.19241-1-will@kernel.org
next prev parent reply other threads:[~2020-05-06 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:28 Will Deacon
2020-05-06 14:36 ` Paul E. McKenney [this message]
2020-05-06 14:41 ` Will Deacon
2020-05-06 15:26 ` Marco Elver
2020-05-06 18:02 ` Paul E. McKenney
2020-05-06 19:11 ` Marco Elver
2020-05-06 19:37 ` Paul E. McKenney
2020-05-06 21:47 ` Paul E. McKenney
2020-05-07 9:34 ` Marco Elver
2020-05-07 15:32 ` 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=20200506143616.GY2869@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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
all inboxes | Powered by JetHome®