On Sun, Jun 09, 2024 at 09:04:14AM +0900, Akira Yokosawa wrote: > 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@xxxxxxxxxx> > >>>>> Signed-off-by: Paul E. McKenney <paulmck@xxxxxxxxxx> > >>>>> Cc: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> > >>>>> Cc: Andrea Parri <parri.andrea@xxxxxxxxx> > >>>>> Cc: Will Deacon <will@xxxxxxxxxx> > >>>>> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx> > >>>>> Cc: Boqun Feng <boqun.feng@xxxxxxxxx> > >>>>> Cc: Nicholas Piggin <npiggin@xxxxxxxxx> > >>>>> Cc: David Howells <dhowells@xxxxxxxxxx> > >>>>> Cc: Jade Alglave <j.alglave@xxxxxxxxx> > >>>>> Cc: Luc Maranget <luc.maranget@xxxxxxxx> > >>>>> Cc: Akira Yokosawa <akiyks@xxxxxxxxx> > >>>> > >>>> 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@xxxxxxxxx> > >>> > >>> 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. Ouch! Thank you for keeping up with this! > Can you wait for a while ? No hurry here. It has been this way for some years, so a little while longer is not a disaster. Thanx, Paul
