From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
To: <jikos@kernel.org>, <benjamin.tissoires@redhat.com>,
<linux-input@vger.kernel.org>
Cc: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Subject: [PATCH 1/5] HID: amd_sfh: Remove unnecessary log
Date: Tue, 9 May 2023 12:28:53 +0530 [thread overview]
Message-ID: <20230509065857.4170013-2-Basavaraj.Natikar@amd.com> (raw)
In-Reply-To: <20230509065857.4170013-1-Basavaraj.Natikar@amd.com>
There is a duplicate log message that is not necessary. Hence remove
unnecessary log message.
Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
---
drivers/hid/amd-sfh-hid/amd_sfh_client.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/hid/amd-sfh-hid/amd_sfh_client.c b/drivers/hid/amd-sfh-hid/amd_sfh_client.c
index d9b7b01900b5..7e4a3b6c0ac7 100644
--- a/drivers/hid/amd-sfh-hid/amd_sfh_client.c
+++ b/drivers/hid/amd-sfh-hid/amd_sfh_client.c
@@ -306,10 +306,6 @@ int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata)
}
} else {
cl_data->sensor_sts[i] = SENSOR_DISABLED;
- dev_dbg(dev, "sid 0x%x (%s) status 0x%x\n",
- cl_data->sensor_idx[i],
- get_sensor_name(cl_data->sensor_idx[i]),
- cl_data->sensor_sts[i]);
}
dev_dbg(dev, "sid 0x%x (%s) status 0x%x\n",
cl_data->sensor_idx[i], get_sensor_name(cl_data->sensor_idx[i]),
--
2.25.1
next prev parent reply other threads:[~2023-05-09 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 6:58 [PATCH 0/5] cleanups to amd-sfh Basavaraj Natikar
2023-05-09 6:58 ` Basavaraj Natikar [this message]
2023-05-09 6:58 ` [PATCH 2/5] HID: amd_sfh: Remove duplicate cleanup Basavaraj Natikar
2023-05-09 6:58 ` [PATCH 3/5] HID: amd_sfh: Split sensor and HID initialization Basavaraj Natikar
2023-05-09 6:58 ` [PATCH 4/5] HID: amd_sfh: Remove duplicate cleanup for SFH1.1 Basavaraj Natikar
2023-05-09 6:58 ` [PATCH 5/5] HID: amd_sfh: Split sensor and HID initialization " Basavaraj Natikar
2023-05-23 13:59 ` [PATCH 0/5] cleanups to amd-sfh Jiri Kosina
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=20230509065857.4170013-2-Basavaraj.Natikar@amd.com \
--to=basavaraj.natikar@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.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