Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755333AbbLEAcx (ORCPT ); Fri, 4 Dec 2015 19:32:53 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:52158 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753981AbbLEAcw (ORCPT ); Fri, 4 Dec 2015 19:32:52 -0500 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Fri, 4 Dec 2015 16:33:32 -0800 From: "Paul E. McKenney" To: Josh Triplett Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@efficios.com, tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com Subject: Re: [PATCH tip/core/rcu 1/8] documentation: Record RCU requirements Message-ID: <20151205003332.GG28602@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20151204234952.GA22805@linux.vnet.ibm.com> <1449273026-23633-1-git-send-email-paulmck@linux.vnet.ibm.com> <20151205000719.GB26663@cloud> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151205000719.GB26663@cloud> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15120500-8236-0000-0000-0000141844CA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2864 Lines: 53 On Fri, Dec 04, 2015 at 04:07:19PM -0800, Josh Triplett wrote: > On Fri, Dec 04, 2015 at 03:50:19PM -0800, Paul E. McKenney wrote: > > This commit adds RCU requirements as published in a 2015 LWN series. > > Bringing these requirements in-tree allows them to be updated as changes > > are discovered. > > > > Signed-off-by: Paul E. McKenney > > --- > > .../RCU/Design/Requirements/2013-08-is-it-dead.png | Bin 0 -> 100825 bytes > > .../Design/Requirements/GPpartitionReaders1.svg | 374 +++ > > .../RCU/Design/Requirements/RCUApplicability.svg | 237 ++ > > .../Design/Requirements/ReadersPartitionGP1.svg | 639 +++++ > > .../RCU/Design/Requirements/Requirements.html | 2799 ++++++++++++++++++++ > > .../RCU/Design/Requirements/Requirements.htmlx | 2643 ++++++++++++++++++ > > Documentation/RCU/Design/htmlqqz.sh | 108 + > > 7 files changed, 6800 insertions(+) > > create mode 100644 Documentation/RCU/Design/Requirements/2013-08-is-it-dead.png > > create mode 100644 Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg > > create mode 100644 Documentation/RCU/Design/Requirements/RCUApplicability.svg > > create mode 100644 Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg > > create mode 100644 Documentation/RCU/Design/Requirements/Requirements.html > > create mode 100644 Documentation/RCU/Design/Requirements/Requirements.htmlx > > If Requirements.html is machine-generated and shouldn't be hand-edited, > and it can be generated without any special tools, then I don't think it > should be committed in the tree; I'd suggest putting it in .gitignore > and generating it from one of the various "make docs" invocations. I considered doing that, but then decided that it is nice for people to be able train their browser directly on the file without having to know what scripts to run. Hmmm... I suppose I could construct a Makefile that dealt with that though... I will give this some thought, and if it looks good, I will add the Makefiles and "git rm" the .htmlx files. > Alternatively, if you want to make sure a usable version is in-tree, you > could make the script reversible (easy enough to do if the compiled > version includes some marker comments or similar), and then tell people > to run it in reverse mode, edit, and run it in forward mode. Then you > don't need the .htmlx file at all. :) Decades ago, back when I (against all evidence) believed I could consistently avoid making stupid mistakes, you might have been able to convince me that this was a good idea. ;-) Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/