perfbook.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Elad Lahav <e2lahav@gmail.com>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	johann@jklaehn.de, sj38.park@gmail.com, maplewish117@gmail.com,
	zhouzhouyi@gmail.com, perfbook@vger.kernel.org
Subject: Re: And, at long last, another perfbook release
Date: Mon, 26 Sep 2022 16:52:51 -0700	[thread overview]
Message-ID: <20220926235251.GB4196@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <CAJbg=FXEQfoKMyGK3Cz63eQRDG-Q=TSrHuuOv-JEYdDfx6T7Xg@mail.gmail.com>

I would be happy to double your percentage, but given that it is a
percentage of zero, this might not make all that much difference.  ;-)

							Thanx, Paul

On Mon, Sep 26, 2022 at 07:24:39PM -0400, Elad Lahav wrote:
> Unless one of these options bumps me up to a higher royalty tier when
> the book becomes a best-seller, I'm fine with any of them.
> 
> --Elad
> 
> On Mon, 26 Sept 2022 at 10:31, Akira Yokosawa <akiyks@gmail.com> wrote:
> >
> > On Mon, 26 Sep 2022 06:56:47 -0700, Paul E. McKenney wrote:
> > > On Mon, Sep 26, 2022 at 09:05:52PM +0900, Akira Yokosawa wrote:
> > >> Hi Paul,
> > >>
> > >> On Sun, 25 Sep 2022 15:50:24 -0700, Paul E. McKenney wrote:
> > >>> Hello!
> > >>>
> > >>> The new v2022.09.25a release of perfbook is available, and the draft
> > >>> announcement is here:  https://paulmck.livejournal.com/68537.html
> > >>> Thank you all for your contributions to this release!
> > >>>
> > >>> Please let me know if changes are needed.
> > >>
> > >> Not on my contribution, but
> > >>
> > >>     The code samples now use C11 thread-local storage instead of the
> > >>     GCC __thread storage class, courtesy of Elad Lahav.
> > >>
> > >> IIUC, Elad touched one of many code samples, namely count_end.c.
> > >> So the conversion has just started.
> > >>
> > >> For me, Elad's contribution of adding QNX as a platform for building
> > >> code samples looks much more interesting.
> > >
> > > Both good points, thank you!
> > >
> > > I updated that paragraph as follows:
> > >
> > >       One of the code samples now use C11 thread-local storage instead
> > >       of the GCC __thread storage class, courtesy of Elad Lahav. Elad
> > >       also added support for building code samples on QNX.
> > >
> > > Does that work better?
> >
> > Works for me!
> >
> >         Thanks, Akira
> >
> > >
> > >                                                       Thanx, Paul
> > >
> > >> Just my 2 cents.
> > >>
> > >>          Thanks, Akira
> > >>
> > >>>                                           If I don't hear otherwise, I
> > >>> will post this more widely by the end of tomorrow (Monday), Pacific Time.
> > >>>
> > >>>                                                     Thanx, Paul

      reply	other threads:[~2022-09-26 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 22:50 And, at long last, another perfbook release Paul E. McKenney
2022-09-26 12:05 ` Akira Yokosawa
2022-09-26 13:56   ` Paul E. McKenney
2022-09-26 14:31     ` Akira Yokosawa
2022-09-26 23:24       ` Elad Lahav
2022-09-26 23:52         ` Paul E. McKenney [this message]

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=20220926235251.GB4196@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=e2lahav@gmail.com \
    --cc=johann@jklaehn.de \
    --cc=maplewish117@gmail.com \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    --cc=zhouzhouyi@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).