From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: allow building with kcov coverage on ARM64
Date: Wed, 15 Jun 2016 10:25:10 +0100 [thread overview]
Message-ID: <20160615092509.GA3984@leverpostej> (raw)
In-Reply-To: <CAG_fn=X521a9uD1bthDZ-swO9hrfq=jE2C_LUvzkn6C_q5dBvA@mail.gmail.com>
On Tue, Jun 14, 2016 at 08:16:08PM +0200, Alexander Potapenko wrote:
> On Tue, Jun 14, 2016 at 7:55 PM, Mark Rutland <mark.rutland@arm.com> wrote:
> > I built and booted (via EFI) a kernel with this feature enabled (also
> > with the boot/Makefile change removed). I haven't tested the feature
> > itself as such, as I'm not sure how to do that.
> You can test it by running the test program from Documentation/kcov.txt.
Ah, I hadn't spotted that. If I get the chance I'll try to give that a
go.
> > FWIW, with the boot/Makefile change removed, feel free to add:
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> Thank you!
> I'll wait till tomorrow for others to comment, and then will send the
> updated version.
Sounds good to me.
Mark.
next prev parent reply other threads:[~2016-06-15 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 16:57 [PATCH v2] arm64: allow building with kcov coverage on ARM64 Alexander Potapenko
2016-06-14 17:16 ` Alexander Potapenko
2016-06-14 17:55 ` Mark Rutland
2016-06-14 18:16 ` Alexander Potapenko
2016-06-15 9:25 ` Mark Rutland [this message]
2016-06-15 11:44 ` Mark Rutland
2016-06-15 11:53 ` Alexander Potapenko
2016-06-15 14:25 ` Mark Rutland
2016-06-15 14:36 ` Dmitry Vyukov
2016-06-15 15:05 ` Mark Rutland
2016-06-15 15:16 ` Dmitry Vyukov
2016-06-16 10:47 ` James Morse
2016-06-16 15:20 ` Alexander Potapenko
2016-06-16 15:44 ` Mark Rutland
2016-06-16 16:25 ` Catalin Marinas
2016-06-16 16:32 ` Mark Rutland
2016-06-16 16:36 ` Alexander Potapenko
2016-06-16 16:36 ` James Morse
2016-06-16 16:39 ` Catalin Marinas
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=20160615092509.GA3984@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).