public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	kernel-team@meta.com, mingo@kernel.org,
	stern@rowland.harvard.edu, parri.andrea@gmail.com,
	will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
	npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
	luc.maranget@inria.fr, Marco Elver <elver@google.com>,
	Daniel Lustig <dlustig@nvidia.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation
Date: Sun, 9 Jun 2024 09:04:14 +0900	[thread overview]
Message-ID: <a3ff0522-fd2d-4c87-9c7b-00cbdd5f3c68@gmail.com> (raw)
In-Reply-To: <6bb5f789-f143-493c-a804-62b7c81dabb0@paulmck-laptop>

On 2024/06/09 0:48, Paul E. McKenney wrote:
> On Sat, Jun 08, 2024 at 08:38:12AM +0900, Akira Yokosawa wrote:
>> On 2024/06/05 13:02, Paul E. McKenney wrote:
>>> On Wed, Jun 05, 2024 at 10:57:27AM +0900, Akira Yokosawa wrote:
>>>> On Tue,  4 Jun 2024 15:14:19 -0700, Paul E. McKenney wrote:
>>>>> Add a citation to Marco's LF mentorship session presentation entitled
>>>>> "The Kernel Concurrency Sanitizer"
>>>>>
>>>>> [ paulmck: Apply Marco Elver feedback. ]
>>>>>
>>>>> Reported-by: Marco Elver <elver@google.com>
>>>>> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>>>>> Cc: Alan Stern <stern@rowland.harvard.edu>
>>>>> Cc: Andrea Parri <parri.andrea@gmail.com>
>>>>> Cc: Will Deacon <will@kernel.org>
>>>>> Cc: Peter Zijlstra <peterz@infradead.org>
>>>>> Cc: Boqun Feng <boqun.feng@gmail.com>
>>>>> Cc: Nicholas Piggin <npiggin@gmail.com>
>>>>> Cc: David Howells <dhowells@redhat.com>
>>>>> Cc: Jade Alglave <j.alglave@ucl.ac.uk>
>>>>> Cc: Luc Maranget <luc.maranget@inria.fr>
>>>>> Cc: Akira Yokosawa <akiyks@gmail.com>
>>>>
>>>> Paul,
>>>>
>>>> While reviewing this, I noticed that
>>>> tools/memory-model/Documentation/README has no mention of
>>>> access-marking.txt.
>>>>
>>>> It has no mention of glossary.txt or locking.txt, either.
>>>>
>>>> I'm not sure where are the right places in README for them.
>>>> Can you update it in a follow-up change?
>>>>
>>>> Anyway, for this change,
>>>>
>>>> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
>>>
>>> Thank you, and good catch!  Does the patch below look appropriate?
>>
>> Well, I must say this is not what I expected.
>> Please see below.
> 
> OK, I was clearly in way too much of a hurry when doing this, and please
> accept my apologies for my inattention.  I am therefore going to do
> what I should have done in the first place, which is to ask you if you
> would like to send a patch fixing this.  If so, I would be quite happy
> to replace mine with yours.

OK.
I think I can submit a draft patch after fixing perfbook's build error
caused by changes in core LaTeX packages released last week.

Can you wait for a while ?

        Thanks, Akira

  reply	other threads:[~2024-06-09  0:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 22:14 [PATCH memory-model 0/3] LKMM updates for v6.11 Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 1/3] tools/memory-model: Add atomic_and()/or()/xor() and add_negative Paul E. McKenney
2024-06-05  0:27   ` Akira Yokosawa
2024-06-05  4:06     ` Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 2/3] tools/memory-model: Add atomic_andnot() with its variants Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation Paul E. McKenney
2024-06-04 23:11   ` Andrea Parri
2024-06-05  4:02     ` Paul E. McKenney
2024-06-05  1:57   ` Akira Yokosawa
2024-06-05  4:02     ` Paul E. McKenney
2024-06-07 23:38       ` Akira Yokosawa
2024-06-08 15:48         ` Paul E. McKenney
2024-06-09  0:04           ` Akira Yokosawa [this message]
2024-06-09  3:10             ` Paul E. McKenney
2024-06-05  7:52   ` Marco Elver
2024-06-05 17:57     ` 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=a3ff0522-fd2d-4c87-9c7b-00cbdd5f3c68@gmail.com \
    --to=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=elver@google.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@meta.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=mingo@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --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