From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, Ingo Molnar <mingo@kernel.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: Wed, 10 Jun 2015 18:36:45 +0200 [thread overview]
Message-ID: <5578679D.2030307@gmail.com> (raw)
In-Reply-To: <20150610145804.GG2753@linux-mips.org>
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.
next parent reply other threads:[~2015-06-10 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55759543.1010408@gmail.com>
[not found] ` <20150610145804.GG2753@linux-mips.org>
2015-06-10 16:36 ` Xose Vazquez Perez [this message]
2015-06-11 6:24 ` Generic kernel features that need architecture(mips) support Ingo Molnar
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=5578679D.2030307@gmail.com \
--to=xose.vazquez@gmail.com \
--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=mingo@kernel.org \
--cc=ralf@linux-mips.org \
/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 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).