From: Guenter Roeck <linux@roeck-us.net>
To: Lukas Bulwahn <lbulwahn@redhat.com>,
Akshay Gupta <akshay.gupta@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] hwmon: clean up Makefile after sbrmi driver movement
Date: Mon, 16 Jun 2025 07:38:39 -0700 [thread overview]
Message-ID: <a749c234-e4e4-4c89-9f26-7f5aa7129c26@roeck-us.net> (raw)
In-Reply-To: <20250529033933.281845-1-lukas.bulwahn@redhat.com>
On 5/28/25 20:39, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit e15658676405 ("hwmon/misc: amd-sbi: Move core sbrmi from hwmon to
> misc") removes the config SENSORS_SBRMI, but misses the reference to that
> config in the Makefile.
>
> Clean up that obsolete line in the Makefile.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
The hardware monitoring mailing list was not copied, meaning
I almost missed this patch. Since the list wasn't copied, I assume
that someone else is supposed to pick it up. Ok with me.
Acked-by: Guenter Roeck <linux@roeck-us.net>
Guenter
> ---
> drivers/hwmon/Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/hwmon/Makefile b/drivers/hwmon/Makefile
> index 48e5866c0c9a..726ffd9f6a1b 100644
> --- a/drivers/hwmon/Makefile
> +++ b/drivers/hwmon/Makefile
> @@ -196,7 +196,6 @@ obj-$(CONFIG_SENSORS_PWM_FAN) += pwm-fan.o
> obj-$(CONFIG_SENSORS_QNAP_MCU_HWMON) += qnap-mcu-hwmon.o
> obj-$(CONFIG_SENSORS_RASPBERRYPI_HWMON) += raspberrypi-hwmon.o
> obj-$(CONFIG_SENSORS_SBTSI) += sbtsi_temp.o
> -obj-$(CONFIG_SENSORS_SBRMI) += sbrmi.o
> obj-$(CONFIG_SENSORS_SCH56XX_COMMON)+= sch56xx-common.o
> obj-$(CONFIG_SENSORS_SCH5627) += sch5627.o
> obj-$(CONFIG_SENSORS_SCH5636) += sch5636.o
prev parent reply other threads:[~2025-06-16 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 3:39 Lukas Bulwahn
2025-06-16 14:38 ` Guenter Roeck [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=a749c234-e4e4-4c89-9f26-7f5aa7129c26@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akshay.gupta@amd.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=naveenkrishna.chatradhi@amd.com \
/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
all inboxes | Powered by JetHome®