From: Catalin Marinas <catalin.marinas@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: David Long <dave.long@linaro.org>,
daniel.thompson@linaro.org, linux-doc@vger.kernel.org,
marc.zyngier@arm.com, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
sparclinux@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations
Date: Mon, 15 Aug 2016 16:41:14 +0100 [thread overview]
Message-ID: <20160815154114.GG22320@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160815093243.4576258a@lwn.net>
On Mon, Aug 15, 2016 at 09:32:43AM -0600, Jonathan Corbet wrote:
> On Mon, 15 Aug 2016 10:49:36 -0400
> David Long <dave.long@linaro.org> wrote:
>
> > On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
> > > On Fri, 12 Aug 2016 16:24:44 -0400
> > > David Long <dave.long@linaro.org> wrote:
> > >
> > >> Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack
> > >> duplication for jprobes problematic. Document this.
> > >
> > > Applied to the docs tree, thanks.
> > >
> > > jon
> >
> > Was kind of hoping to see an ack (or critique) from a sparc maintainer.
>
> So are you saying you don't want the patch applied at this point?
To avoid any doubt, for arm64:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
(and I want the patch applied)
prev parent reply other threads:[~2016-08-15 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 20:24 David Long
2016-08-12 23:46 ` Masami Hiramatsu
2016-08-15 14:25 ` Jonathan Corbet
2016-08-15 14:49 ` David Long
2016-08-15 15:32 ` Jonathan Corbet
2016-08-15 15:41 ` David Long
2016-08-15 15:41 ` Catalin Marinas [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=20160815154114.GG22320@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=dave.long@linaro.org \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mhiramat@kernel.org \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®