All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: elver@google.com, glider@google.com, lkp@intel.com,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: [folded-merged] printk-introduce-dump_stack_lvl-fix.patch removed from -mm tree
Date: Mon, 28 Jun 2021 17:30:32 -0700	[thread overview]
Message-ID: <20210629003032.yBwY2eCIH%akpm@linux-foundation.org> (raw)


The patch titled
     Subject: fix for "printk: introduce dump_stack_lvl()"
has been removed from the -mm tree.  Its filename was
     printk-introduce-dump_stack_lvl-fix.patch

This patch was dropped because it was folded into printk-introduce-dump_stack_lvl.patch

------------------------------------------------------
From: Marco Elver <elver@google.com>
Subject: fix for "printk: introduce dump_stack_lvl()"

Add missing dump_stack_lvl() stub if CONFIG_PRINTK=n.

Link: https://lkml.kernel.org/r/YJ0KAM0hQev1AmWe@elver.google.com
Signed-off-by: Marco Elver <elver@google.com>
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Alexander Potapenko <glider@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 include/linux/printk.h |    4 ++++
 1 file changed, 4 insertions(+)

--- a/include/linux/printk.h~printk-introduce-dump_stack_lvl-fix
+++ a/include/linux/printk.h
@@ -270,6 +270,10 @@ static inline void show_regs_print_info(
 {
 }
 
+static inline void dump_stack_lvl(const char *log_lvl)
+{
+}
+
 static inline void dump_stack(void)
 {
 }
_

Patches currently in -mm which might be from elver@google.com are

printk-introduce-dump_stack_lvl.patch
kfence-unconditionally-use-unbound-work-queue.patch
kcov-add-__no_sanitize_coverage-to-fix-noinstr-for-all-architectures.patch
kcov-add-__no_sanitize_coverage-to-fix-noinstr-for-all-architectures-v2.patch
kcov-add-__no_sanitize_coverage-to-fix-noinstr-for-all-architectures-v3.patch


                 reply	other threads:[~2021-06-29  0:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210629003032.yBwY2eCIH%akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.