linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Evan Green <evgreen@chromium.org>,
	Hsin-Yi Wang <hsinyi@chromium.org>,
	Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v4 05/13] module: Add printk formats to add module build ID to stacktraces
Date: Mon, 19 Apr 2021 12:34:09 +0200	[thread overview]
Message-ID: <YH1coYBRn3pNs4gu@gunter> (raw)
In-Reply-To: <161871075477.46595.10848605889976259732@swboyd.mtv.corp.google.com>

+++ Stephen Boyd [17/04/21 18:52 -0700]:
[snip]
>Sounds good. It means that some more ifdefs are probably required vs.
>making the array size be 0 when the config is disabled but that isn't a
>big problem for me. I'm reworking the code now and will test and then
>send v5 shortly. Thanks!

Great, thanks a lot Stephen!

Jessica

  reply	other threads:[~2021-04-19 10:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10  1:52 [PATCH v4 00/13] Add build ID to stacktraces Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 01/13] buildid: Only consider GNU notes for build ID parsing Stephen Boyd
2021-04-13 14:34   ` Petr Mladek
2021-04-10  1:52 ` [PATCH v4 02/13] buildid: Add API to parse build ID out of buffer Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 03/13] buildid: Stash away kernels build ID on init Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 04/13] dump_stack: Add vmlinux build ID to stack traces Stephen Boyd
2021-04-13 14:41   ` Petr Mladek
2021-04-13 20:36     ` Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 05/13] module: Add printk formats to add module build ID to stacktraces Stephen Boyd
2021-04-12 11:58   ` Andy Shevchenko
2021-04-12 19:29     ` Stephen Boyd
2021-04-13 10:56       ` Andy Shevchenko
2021-04-13 15:16         ` Petr Mladek
2021-04-13 20:10           ` Stephen Boyd
2021-04-13 22:36             ` Stephen Boyd
2021-04-13 15:01   ` Petr Mladek
2021-04-13 22:57     ` Stephen Boyd
2021-04-15  8:53       ` Petr Mladek
2021-04-15 13:04   ` Jessica Yu
2021-04-18  1:52     ` Stephen Boyd
2021-04-19 10:34       ` Jessica Yu [this message]
2021-04-10  1:52 ` [PATCH v4 06/13] arm64: stacktrace: Use %pSb for backtrace printing Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 07/13] x86/dumpstack: Use %pSb/%pBb " Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 08/13] scripts/decode_stacktrace.sh: Support debuginfod Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 09/13] scripts/decode_stacktrace.sh: Silence stderr messages from addr2line/nm Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 10/13] scripts/decode_stacktrace.sh: Indicate 'auto' can be used for base path Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 11/13] buildid: Mark some arguments const Stephen Boyd
2021-04-10  1:52 ` [PATCH v4 12/13] buildid: Fix kernel-doc notation Stephen Boyd
2021-04-10  1:53 ` [PATCH v4 13/13] kdump: Use vmlinux_build_id to simplify Stephen Boyd

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=YH1coYBRn3pNs4gu@gunter \
    --to=jeyu@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ast@kernel.org \
    --cc=evgreen@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=jolsa@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=swboyd@chromium.org \
    --cc=willy@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).