[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fbb89aa4-3e1c-42bf-8202-4f35e2dcb17b@paulmck-laptop>
Date: Sat, 8 Jun 2024 20:10:58 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Akira Yokosawa <akiyks@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
kernel-team@...a.com, mingo@...nel.org, stern@...land.harvard.edu,
parri.andrea@...il.com, will@...nel.org, peterz@...radead.org,
boqun.feng@...il.com, npiggin@...il.com, dhowells@...hat.com,
j.alglave@....ac.uk, luc.maranget@...ia.fr,
Marco Elver <elver@...gle.com>, Daniel Lustig <dlustig@...dia.com>,
Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF
mentorship session citation
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@...gle.com>
> >>>>> Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
> >>>>> Cc: Alan Stern <stern@...land.harvard.edu>
> >>>>> Cc: Andrea Parri <parri.andrea@...il.com>
> >>>>> Cc: Will Deacon <will@...nel.org>
> >>>>> Cc: Peter Zijlstra <peterz@...radead.org>
> >>>>> Cc: Boqun Feng <boqun.feng@...il.com>
> >>>>> Cc: Nicholas Piggin <npiggin@...il.com>
> >>>>> Cc: David Howells <dhowells@...hat.com>
> >>>>> Cc: Jade Alglave <j.alglave@....ac.uk>
> >>>>> Cc: Luc Maranget <luc.maranget@...ia.fr>
> >>>>> Cc: Akira Yokosawa <akiyks@...il.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@...il.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.
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
Powered by blists - more mailing lists