From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Junchang Wang <junchangwang@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Release/edition plans
Date: Fri, 19 Oct 2018 11:19:42 -0700 [thread overview]
Message-ID: <20181019181942.GM2674@linux.ibm.com> (raw)
In-Reply-To: <CABoNC82vvvnnBjq251vMQwdvnJdcZ0emFHX1yhkMO-eVLoYk2g@mail.gmail.com>
Hello, Junchang,
I don't have any specific advise. Reading it sequentially is a very
reasonable approach, as is preferentially reading sections of specific
interest to you. You are the one doing the reading, so your choice. ;-)
Thanx, Paul
On Fri, Oct 19, 2018 at 11:07:34PM +0800, Junchang Wang wrote:
> Hi Paul,
>
> Sorry for the late reply; I was overwhelmed by some other jobs in the
> past weeks.
>
> It sounds great that you will release out a new version by the end of
> this year. I have some time in the following one and a half months and
> is going to read through the book. I'm not an expert in this domain
> yet but would be very happy to help improve the book :-). Please let
> me if you have some suggestions; otherwise, I will read
> chapter-by-chapter since next week.
>
>
> Thanks,
> --Junchang
> On Fri, Oct 19, 2018 at 4:35 AM Paul E. McKenney <paulmck@linux.ibm.com> wrote:
> >
> > Hello!
> >
> > I would normally have done a perfbook release by now, given that the last
> > one was in November 2017. My lame excuse is that creating 340 RCU/LKMM
> > patches thus far this year turned out to be a bit harder than it looks.
> >
> > My current thought is to get a release out in the next month or two,
> > and to get the second edition out in 2019.
> >
> > Thoughts?
> >
> > Thanx, Paul
> >
>
next prev parent reply other threads:[~2018-10-20 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 20:34 Release/edition plans Paul E. McKenney
2018-10-19 15:07 ` Junchang Wang
2018-10-19 18:19 ` Paul E. McKenney [this message]
2018-10-28 15:19 ` Akira Yokosawa
2018-10-28 17:16 ` Paul E. McKenney
2018-10-30 22:33 ` 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=20181019181942.GM2674@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=junchangwang@gmail.com \
--cc=perfbook@vger.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