From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Luc Maranget <luc.maranget@inria.fr>,
Jade Alglave <j.alglave@ucl.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -lkmm] tools/memory-model/README: Update klitmus7 compat table
Date: Fri, 6 May 2022 11:55:02 +0900 [thread overview]
Message-ID: <18d2ad1d-c2a5-682a-91e8-2d8067e62b30@gmail.com> (raw)
In-Reply-To: <20220502165058.GA1790663@paulmck-ThinkPad-P17-Gen-1>
On Mon, 2 May 2022 09:50:58 -0700,
Paul E. McKenney wrote:
> On Mon, May 02, 2022 at 09:05:09PM +0900, Akira Yokosawa wrote:
>> EXPORT_SYMBOL of do_exec() was removed in v5.17. Unfortunately,
>> kernel modules from klitmus7 7.56 have do_exec() at the end of
>> each kthread.
>>
>> herdtools7 7.56.1 has addressed the issue.
>>
>> Update the compatibility table accordingly.
>>
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>> Cc: Luc Maranget <luc.maranget@inria.fr>
>> Cc: Jade Alglave <j.alglave@ucl.ac.uk>
>> Cc: stable@vger.kernel.org # v5.17+
>> ---
>> Hi Paul,
>>
>> herdtools7 release 7.56.1 is available at
>> https://github.com/herd/herdtools7/releases/tag/7.56.1,
>> and "opam update/upgrade" should catch it soon.
With the help of Luc, opam repository has accepted 7.56.1.
>
> Good catch, thank you!
>
>> I think this is worth for v5.18, albeit it is a minor update
>> in documentation.
>
> Good point, but let me give it some thought.
On the second thought, as v5.18-rc6 is expected this weekend,
I'm OK if this update makes the next (v5.19) merge window.
This is more of a "news" type update and the "Cc: stable" tag
should work either way.
Thanks, Akira
>
> Thanx, Paul
>
>> Thoughts?
>>
>> Thanks, Akira
[...]
next prev parent reply other threads:[~2022-05-06 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:05 [PATCH -lkmm] tools/memory-model/README: Update klitmus7 compat table Akira Yokosawa
2022-05-02 16:50 ` Paul E. McKenney
2022-05-06 2:55 ` Akira Yokosawa [this message]
2022-05-06 19:04 ` 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=18d2ad1d-c2a5-682a-91e8-2d8067e62b30@gmail.com \
--to=akiyks@gmail.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--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