From: Sachin Sant <sachinp@linux.ibm.com>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH] watchdog: Fix build error when CONFIG_SOFTLOCKUP_DETECTOR is not set
Date: Wed, 27 Jul 2022 15:40:36 +0530 [thread overview]
Message-ID: <23117A1A-0607-4700-95FC-C1F0DCC1E3B0@linux.ibm.com> (raw)
In-Reply-To: <20220727092109.31362-1-ldufour@linux.ibm.com>
> The definition of lockup_detector_reconfigure should be exported even in
> that case, and __lockup_detector_reconfigure should remain static.
>
> Fixes: 24a1260705b7 ("watchdog: export lockup_detector_reconfigure")
> Reported-by: Sachin Sant <sachinp@linux.ibm.com>
> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
> ---
> kernel/watchdog.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks Laurent for the fix.
Tested-by: Sachin Sant <sachinp@linux.ibm.com>
- Sachin
WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@linux.ibm.com>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: Fix build error when CONFIG_SOFTLOCKUP_DETECTOR is not set
Date: Wed, 27 Jul 2022 15:40:36 +0530 [thread overview]
Message-ID: <23117A1A-0607-4700-95FC-C1F0DCC1E3B0@linux.ibm.com> (raw)
In-Reply-To: <20220727092109.31362-1-ldufour@linux.ibm.com>
> The definition of lockup_detector_reconfigure should be exported even in
> that case, and __lockup_detector_reconfigure should remain static.
>
> Fixes: 24a1260705b7 ("watchdog: export lockup_detector_reconfigure")
> Reported-by: Sachin Sant <sachinp@linux.ibm.com>
> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
> ---
> kernel/watchdog.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks Laurent for the fix.
Tested-by: Sachin Sant <sachinp@linux.ibm.com>
- Sachin
next prev parent reply other threads:[~2022-07-27 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 9:21 [PATCH] watchdog: Fix build error when CONFIG_SOFTLOCKUP_DETECTOR is not set Laurent Dufour
2022-07-27 9:21 ` Laurent Dufour
2022-07-27 10:10 ` Sachin Sant [this message]
2022-07-27 10:10 ` Sachin Sant
2022-07-27 11:38 ` Michael Ellerman
2022-07-27 11:38 ` Michael Ellerman
2022-07-27 14:20 ` Laurent Dufour
2022-07-27 14:20 ` Laurent Dufour
2022-07-28 3:18 ` Michael Ellerman
2022-07-28 3:18 ` Michael Ellerman
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=23117A1A-0607-4700-95FC-C1F0DCC1E3B0@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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.