From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
james.morse@arm.com, kaleshsingh@google.com,
madvenka@linux.microsoft.com, maz@kernel.org, tabba@google.com,
will@kernel.org
Subject: Re: [PATCH v3 1/9] arm64: stacktrace: fix kerneldoc comments
Date: Tue, 16 Aug 2022 16:59:46 +0100 [thread overview]
Message-ID: <Yvu+8ZR0zP1EUxUF@sirena.org.uk> (raw)
In-Reply-To: <20220815113922.3280255-2-mark.rutland@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 207 bytes --]
On Mon, Aug 15, 2022 at 12:39:14PM +0100, Mark Rutland wrote:
> Many of the comment blocks in the arm64 stacktrace code are *almost*
> kerneldoc, but not quite.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-16 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:39 [PATCH v3 0/9] arm64: stacktrace: cleanups and improvements Mark Rutland
2022-08-15 11:39 ` [PATCH v3 1/9] arm64: stacktrace: fix kerneldoc comments Mark Rutland
2022-08-16 15:59 ` Mark Brown [this message]
2022-08-23 5:11 ` Madhavan T. Venkataraman
2022-08-15 11:39 ` [PATCH v3 2/9] arm64: stacktrace: simplify unwind_next_common() Mark Rutland
2022-08-15 11:39 ` [PATCH v3 3/9] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record() Mark Rutland
2022-08-15 11:39 ` [PATCH v3 4/9] arm64: stacktrace: move SDEI stack helpers to stacktrace code Mark Rutland
2022-08-15 11:39 ` [PATCH v3 5/9] arm64: stacktrace: add stackinfo_on_stack() helper Mark Rutland
2022-08-15 11:39 ` [PATCH v3 6/9] arm64: stacktrace: rework stack boundary discovery Mark Rutland
2022-08-15 11:39 ` [PATCH v3 7/9] arm64: stacktrace: remove stack type from fp translator Mark Rutland
2022-08-15 11:39 ` [PATCH v3 8/9] arm64: stacktrace: track all stack boundaries explicitly Mark Rutland
2022-08-15 11:39 ` [PATCH v3 9/9] arm64: stacktrace: track hyp stacks in unwinder's address space Mark Rutland
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=Yvu+8ZR0zP1EUxUF@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kaleshsingh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=tabba@google.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).