Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752261AbbLEUTL (ORCPT ); Sat, 5 Dec 2015 15:19:11 -0500 Received: from e35.co.us.ibm.com ([32.97.110.153]:48380 "EHLO e35.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751095AbbLEUTK (ORCPT ); Sat, 5 Dec 2015 15:19:10 -0500 X-IBM-Helo: d03dlp03.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Sat, 5 Dec 2015 12:19:37 -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: <20151205201937.GA6063@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> <20151205003443.GC26663@cloud> <20151205015431.GH28602@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151205015431.GH28602@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15120520-0013-0000-0000-00001ACC7928 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3926 Lines: 102 On Fri, Dec 04, 2015 at 05:54:31PM -0800, Paul E. McKenney wrote: > On Fri, Dec 04, 2015 at 04:34:43PM -0800, Josh Triplett wrote: > > The content of the document seems fine; a few comments below on > > meta-issues. > > > > On Fri, Dec 04, 2015 at 03:50:19PM -0800, Paul E. McKenney wrote: > > > --- /dev/null > > > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > > > @@ -0,0 +1,2799 @@ > > > + > > > + > > > + > > + "http://www.w3.org/TR/html4/loose.dtd"> > > > > Nit: these days, this should just be: > > > > Will making this change mean that https://validator.w3.org/ will > then require me to make a huge quantity of other changes? I checked a prominent web site, and they are using the same doctype as I am, so I am keeping this one. However... > > > + > > > + A Tour Through RCU's Requirements [LWN.net] > > > + > > > > Is there a good reason to not use charset=utf-8 here? > > Beats me. Cargo-culted that one. ;-) ... they use utf-8, so I changed mine accordingly. > > > + > > > +

A Tour Through RCU's Requirements

> > > + > > > +

Copyright IBM Corporation, 2015

> > > > If you're aiming for a properly formatted copyright notice, the year > > typically comes first, followed by the copyright holder. That said, > > your corporate guidelines presumably have a specific format; is this > > that format? > > Indeed it is. Between you and IBM Legal, I unfortunately must follow > IBM Legal's advice. ;-) > > > > +

Author: Paul E. McKenney

> > > +

The initial version of this document appeared in the > > > +LWN articles > > > +here, > > > +here, and > > > +here.

> > > > s/http/https/g > > Will change. And done, globally, at least for those whose webservers were willing to put up with the change. Which was the vast majority. [ . . . ] > > > +

> > > +This all should be quite obvious, but the fact remains that > > > +Linus Torvalds recently had to > > > +remind > > > +me of this requirement. > > > > I'd suggest using the lkml.kernel.org redirector for this link, along > > with a Message-Id. > > > > > +

> > > +The name notwithstanding, some Linux-kernel architectures > > > +can have nested NMIs, which RCU must handle correctly. > > > +Andy Lutomirski > > > +surprised me > > > +with this requirement; > > > +he also kindly surprised me with > > > +an algorithm > > > +that meets this requirement. > > > > These links should both use lkml.kernel.org as well. Doubly important > > because lkml.org is often down or has broken messages in its archive. > > Good point, will look into finding the Message-IDs... This involves a second click for https://lkml.kernel.org/r/ Trying https://lkml.kernel.org/g/. Which works nicely, so sold! I will let you bug kernel.org about the fact that it translates the URL to the http: form rather than the https: form... But if it did that for the /g/ form, it couldn't find the web page. Never mind! So all the ones that work have been converted. 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/