Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756141AbcJGG1y (ORCPT ); Fri, 7 Oct 2016 02:27:54 -0400 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:27093 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750974AbcJGG1q (ORCPT ); Fri, 7 Oct 2016 02:27:46 -0400 X-IronPort-AV: E=Sophos;i="5.31,308,1473112800"; d="scan'208";a="239765590" Date: Fri, 7 Oct 2016 08:27:21 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: SF Markus Elfring cc: Julia Lawall , Coccinelle , Gilles Muller , Jonathan Corbet , "Luis R. Rodriguez" , Michal Marek , Nicolas Palix , LKML , kernel-janitors@vger.kernel.org Subject: Re: scripts/coccicheck: Update for a comment? In-Reply-To: <8d36952c-1dbb-bb26-ee57-3e1540c042c0@users.sourceforge.net> Message-ID: References: <76a6d8fa-03b9-5589-2885-fa62933dd391@users.sourceforge.net> <8d36952c-1dbb-bb26-ee57-3e1540c042c0@users.sourceforge.net> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1330 Lines: 37 On Fri, 7 Oct 2016, SF Markus Elfring wrote: > >>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4 > >>> > >>> How about submitting a patch to fix the problem? > >> > >> I would appreciate to become a bit more sure about the current storage location > >> which should be referenced in this file. > > > > In the Documentation directory find . -name "*cocci*" > > > > gives > > > > ./dev-tools/coccinelle.rst > > > > I think you could have done that yourself. > > Does the usage of the format "reStructuredText" trigger further considerations > like the following? > > * Does your feedback suggest that the path from this source file should be put > in related places? > > * Would it make sense to store such a file name in a special variable? > > * When would you refer to generated file formats (like PDF) for this use case? Either you send the patch, or I will send the patch, when I have time, with no credit to you. I'm not an expert on all of the future plans for the documentation, The only think I know is where the file is now, and that the file is perfectly readable in its rst format, and thus it seems quite all right to reference it. If the situation change in the future, we can have another patch in the future. julia