From: Jonathan Corbet <corbet@lwn.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: MIPS supports HAVE_REGS_AND_STACK_ACCESS_API
Date: Thu, 13 Oct 2016 09:15:07 -0600 [thread overview]
Message-ID: <20161013091507.2d6b85f0@lwn.net> (raw)
In-Reply-To: <20161013150936.GA27810@linux-mips.org>
On Thu, 13 Oct 2016 17:09:36 +0200
Ralf Baechle <ralf@linux-mips.org> wrote:
> Jonathan, you can funnel this through the MIPS tree if you're ok with that?
> Just lemme know -- Ralf
Through the MIPS tree is fine with me.
Thanks,
jon
prev parent reply other threads:[~2016-10-13 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 15:09 [PATCH] Documentation: MIPS supports HAVE_REGS_AND_STACK_ACCESS_API Ralf Baechle
2016-10-13 15:15 ` Jonathan Corbet [this message]
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=20161013091507.2d6b85f0@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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