linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Scull <ascull@google.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org,
	 Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7952/12404] arch/arm64/kvm/handle_exit.c:318:4: error: implicit declaration of function 'bug_get_file_line'
Date: Thu, 15 Apr 2021 09:19:03 +0100	[thread overview]
Message-ID: <CADcWuH0vfFu_AdkQr9upS5MHsfgLu+jAY7Q9g8nuN4cdf6_G7A@mail.gmail.com> (raw)
In-Reply-To: <87lf9kn6wb.wl-maz@kernel.org>

> > Andrew,
> >
> > This is what I plan to stick on top of your series. Let me know if
> > you're OK with it.
>
> Duh. And now for the real patch and not the dummy thing that was in my
> sandbox...
>
>         M.
>
> From 882ff4062169d5914ad7ed88c9138a90e485c05e Mon Sep 17 00:00:00 2001
> From: Marc Zyngier <maz@kernel.org>
> Date: Wed, 14 Apr 2021 17:41:14 +0100
> Subject: [PATCH] bug: Provide dummy version of bug_get_file_line() when
>  !GENERIC_BUG
>
> Provide the missing dummy bug_get_file_line() implementation when
> GENENERIC_BUG isn't selected.

Oh, conditional in the Makefile...

>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: 26dbc7e299c7 ("bug: Factor out a getter for a bug's file line")
> Cc: Andrew Scull <ascull@google.com>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
>  include/linux/bug.h | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/bug.h b/include/linux/bug.h
> index e3841bee4c8d..d889ee043118 100644
> --- a/include/linux/bug.h
> +++ b/include/linux/bug.h
> @@ -61,6 +61,12 @@ static inline enum bug_trap_type report_bug(unsigned long bug_addr,
>         return BUG_TRAP_TYPE_BUG;
>  }
>
> +struct bug_entry;
> +static inline void bug_get_file_line(struct bug_entry *bug, const char **file,
> +                                    unsigned int *line)
> +{
> +       *file = NULL;

`line` is also an output argument so it might be worth zeroing even
though it shouldn't really be used if `file` is NULL. Otherwise,
thanks for catching!

> +}
>
>  static inline void generic_bug_clear_once(void) {}
>
> --
> 2.30.2


      reply	other threads:[~2021-04-15  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  4:39 kernel test robot
2021-04-14 16:47 ` Marc Zyngier
2021-04-14 16:54   ` Marc Zyngier
2021-04-15  8:19     ` Andrew Scull [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=CADcWuH0vfFu_AdkQr9upS5MHsfgLu+jAY7Q9g8nuN4cdf6_G7A@mail.gmail.com \
    --to=ascull@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=maz@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