All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, linux-arch@vger.kernel.org,
	linux-api@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Generic kernel features that need architecture(mips) support
Date: Thu, 11 Jun 2015 08:24:53 +0200	[thread overview]
Message-ID: <20150611062452.GB32133@gmail.com> (raw)
In-Reply-To: <5578679D.2030307@gmail.com>


(Jon Cc:-ed)

* Xose Vazquez Perez <xose.vazquez@gmail.com> wrote:

> On 06/10/2015 04:58 PM, Ralf Baechle wrote:
> 
> > How are the documentation files in Documentation/features/ maintained?
> > They were automatically generated so I wonder if I have to take care
> > of anything.
> 
> CC: Ingo and related ml.

So changes to Documentation/features/ should come as simple patches done from hand 
editing, there's no need to preserve any initial (half-)automated generation. 
Formatting should be preserved so that Documentation/features/list-arch.sh still 
works as before.

Jon: would you like to receive all patches to Documentation/features/ so you can 
collect them in the documentation tree, or can maintainers patch it as part of any 
feature work that affects the tables? I think it's all finegrained enough to not 
create conflicts. That way they would become partly self-maintaining. (Or at least 
one can always hope! ;-)

Thanks,

	Ingo

  reply	other threads:[~2015-06-11  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 13:14 Generic kernel features that need architecture(mips) support Xose Vazquez Perez
2015-06-10 14:58 ` Ralf Baechle
2015-06-10 15:57   ` HAVE_CMPXCHG_LOCAL arch support Ralf Baechle
2015-06-10 16:00     ` Peter Zijlstra
2015-06-10 16:36   ` Generic kernel features that need architecture(mips) support Xose Vazquez Perez
2015-06-11  6:24     ` Ingo Molnar [this message]
2015-06-11 13:20       ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150611062452.GB32133@gmail.com \
    --to=mingo@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=xose.vazquez@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.