From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v4.5
Date: Thu, 21 Jan 2016 13:00:21 +0100 [thread overview]
Message-ID: <CAMuHMdWBHU_Y+acaCsW=OrqnxYNdSojD8c0x0B0HTpnyfaS_ZA@mail.gmail.com> (raw)
In-Reply-To: <20160111123518.GA13930@gmail.com>
On Mon, Jan 11, 2016 at 1:35 PM, Ingo Molnar <mingo@kernel.org> wrote:
> Please pull the latest core-rcu-for-linus git tree from:
> One thing I should note is that these pieces of documentation are fairly large
> files:
>
> .../RCU/Design/Requirements/Requirements.html | 2897 ++++++++++++++++++++
> .../RCU/Design/Requirements/Requirements.htmlx | 2741 ++++++++++++++++++
>
> and are written in HTML, not the usual .txt style. I hope they are fine.
Not to mention the PNG image:
> .../RCU/Design/Requirements/2013-08-is-it-dead.png | Bin 0 -> 100825 bytes
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-01-21 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 12:35 [GIT PULL] RCU changes for v4.5 Ingo Molnar
2016-01-11 12:54 ` Paul E. McKenney
2016-01-21 12:00 ` Geert Uytterhoeven [this message]
2016-01-21 16:01 ` Paul E. McKenney
2016-01-21 18:28 ` Geert Uytterhoeven
2016-01-21 19:20 ` Paul E. McKenney
2016-01-21 20:04 ` Geert Uytterhoeven
2016-01-21 20:24 ` 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='CAMuHMdWBHU_Y+acaCsW=OrqnxYNdSojD8c0x0B0HTpnyfaS_ZA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).