From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752683AbcIIOeL (ORCPT ); Fri, 9 Sep 2016 10:34:11 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:53545 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750832AbcIIOeJ (ORCPT ); Fri, 9 Sep 2016 10:34:09 -0400 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com Date: Fri, 9 Sep 2016 07:33:55 -0700 From: "Paul E. McKenney" To: Richard Weinberger Cc: Michael Opdenacker , Jonathan Corbet , Josh Triplett , Steven Rostedt , mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com, LKML , "linux-doc@vger.kernel.org" Subject: Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Reply-To: paulmck@linux.vnet.ibm.com References: <1473428586-16491-1-git-send-email-michael.opdenacker@free-electrons.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16090914-0028-0000-0000-0000058CAC78 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005733; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000185; SDB=6.00755790; UDB=6.00357920; IPR=6.00528745; BA=6.00004705; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012629; XFM=3.00000011; UTC=2016-09-09 14:33:55 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16090914-0029-0000-0000-00002F1527AD Message-Id: <20160909143355.GJ32751@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-09-09_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=12 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609020000 definitions=main-1609090222 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote: > Michael, > > On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker > wrote: > > Fix 4 LKML archive links that became broken (data loss > > on mail-archive.com?) > > > > Working links were found on Paul McKenney's RCU articles > > on LWN.net, from which the documentation originates: > > http://lwn.net/Articles/652156/ > > http://lwn.net/Articles/652677/ > > http://lwn.net/Articles/653326/ > > > > Signed-off-by: Michael Opdenacker > > --- > > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > > index ece410f40436..2adb3d43ce44 100644 > > --- a/Documentation/RCU/Design/Requirements/Requirements.html > > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > > bloatwatch > > efforts, memory footprint is critically important on single-CPU systems with > > non-preemptible (CONFIG_PREEMPT=n) kernels, and thus > > -tiny RCU > > +tiny RCU > > was born. > > Josh Triplett has since taken over the small-memory banner with his > > Linux kernel tinification > > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > > and cleaned up with destroy_rcu_head(). > > Mathieu Desnoyers made me aware of this requirement, and also > > supplied the needed > > - patch. > > + patch. > > Please don't add lkml.org. It does not use message ids for indexing. > With knowing the message id you can query any other archive. > e.g. http://marc.info/?i=20100319013024.GA28456@Krystal > By adding lkml.org you kill that information. Archives come and go, > the message id is the only common query id we have. > > IMHO kernel.org admins should fix/improve their redirection service to > point to a working service. There has been some instability in the kernel.org redirection. Right now, the /r/ services seems to work, though as noted the /g/ does not. Please report this to the Kernel.org administrators: https://kernel.org/category/contact-us.html Thanx, Paul