From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752877AbdJLTCc (ORCPT <rfc822;w@1wt.eu>);
        Thu, 12 Oct 2017 15:02:32 -0400
Received: from aserp1040.oracle.com ([141.146.126.69]:27849 "EHLO
        aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751542AbdJLTCa (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 12 Oct 2017 15:02:30 -0400
Date: Thu, 12 Oct 2017 14:01:25 -0500
From: Tom Saeger <tom.saeger@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tom Saeger <tom.saeger@oracle.com>, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (1)
Message-ID: <20171012190125.x4hv4wcksocvjpcb@revenge.us.oracle.com>
References: <cover.1507653969.git.tom.saeger@oracle.com>
 <20171012112425.7f67cfca@lwn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171012112425.7f67cfca@lwn.net>
User-Agent: NeoMutt/20170912 (1.9.0)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Oct 12, 2017 at 05:24:25PM +0000, Jonathan Corbet wrote:
> On Tue, 10 Oct 2017 12:35:58 -0500
> Tom Saeger <tom.saeger@oracle.com> wrote:
> 
> > Recently, while reading up on binfmt I attempted to open a document ref
> > only to find it was invalid.  I did a quick grep, found all the
> > binfmt_misc related broken refs and sent a patch.
> > 
> > Fine. Easy.
> > 
> > Then I wondered, "how many broken doc refs are there?".
> > 
> > Turns out with all the recent doc moves, quite a few.
> > 
> > I went about fixing just those found in Documentation/,
> > except those in Documentation/translations/ and
> > Documentation/devicetree/ for now.
> > 
> > Most of these changes were s/txt/rst/ or fixing up a path to an obvious
> > new location.  Some required going back to v4.10 v4.4 or some other
> > version to sleuth-out what content was actually being referenced and
> > then fixing the reference to point to the new file with that content.
> > 
> > This is batch 1.
> 
> I've applied the set to the docs tree, thanks.
> 
> jon

Thanks Jon.  I'll send another batch soon.

--Tom