* Re: Generic kernel features that need architecture(mips) support [not found] ` <20150610145804.GG2753@linux-mips.org> @ 2015-06-10 16:36 ` Xose Vazquez Perez 2015-06-11 6:24 ` Ingo Molnar 0 siblings, 1 reply; 3+ messages in thread From: Xose Vazquez Perez @ 2015-06-10 16:36 UTC (permalink / raw) To: Ralf Baechle; +Cc: linux-mips, Ingo Molnar, linux-arch, linux-api, LKML 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Generic kernel features that need architecture(mips) support 2015-06-10 16:36 ` Generic kernel features that need architecture(mips) support Xose Vazquez Perez @ 2015-06-11 6:24 ` Ingo Molnar 2015-06-11 13:20 ` Jonathan Corbet 0 siblings, 1 reply; 3+ messages in thread From: Ingo Molnar @ 2015-06-11 6:24 UTC (permalink / raw) To: Xose Vazquez Perez, Jonathan Corbet Cc: Ralf Baechle, linux-mips, linux-arch, linux-api, LKML (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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Generic kernel features that need architecture(mips) support 2015-06-11 6:24 ` Ingo Molnar @ 2015-06-11 13:20 ` Jonathan Corbet 0 siblings, 0 replies; 3+ messages in thread From: Jonathan Corbet @ 2015-06-11 13:20 UTC (permalink / raw) To: Ingo Molnar Cc: Xose Vazquez Perez, Ralf Baechle, linux-mips, linux-arch, linux-api, LKML On Thu, 11 Jun 2015 08:24:53 +0200 Ingo Molnar <mingo@kernel.org> wrote: > 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! ;-) I sort of figured I'd handle it the way I do the rest of Documentation/ — I'm happy to herd the patches, but I also have no problem staying out of the way when other maintainers reach into it. jon ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-06-11 13:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <55759543.1010408@gmail.com>
[not found] ` <20150610145804.GG2753@linux-mips.org>
2015-06-10 16:36 ` Generic kernel features that need architecture(mips) support Xose Vazquez Perez
2015-06-11 6:24 ` Ingo Molnar
2015-06-11 13:20 ` Jonathan Corbet
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).