From: Thomas Andreatta <thomasandreatta2000@gmail.com>
To: hansg@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Thomas Andreatta <thomas.andreatta2000@gmail.com>
Subject: [PATCH 1/4 V2] Staging: media: atomisp: i2c: removed redundand debug message
Date: Thu, 19 Jun 2025 10:44:18 +0200 [thread overview]
Message-ID: <20250619084420.146151-1-thomas.andreatta2000@gmail.com> (raw)
Checkpatch fix: deleted `dev_dbg()` printing the name of the function.
ftrace can be used instead.
Signed-off-by: Thomas Andreatta <thomas.andreatta2000@gmail.com>
---
drivers/staging/media/atomisp/i2c/atomisp-gc0310.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/media/atomisp/i2c/atomisp-gc0310.c b/drivers/staging/media/atomisp/i2c/atomisp-gc0310.c
index d35394f1ddbb..830a38086cb8 100644
--- a/drivers/staging/media/atomisp/i2c/atomisp-gc0310.c
+++ b/drivers/staging/media/atomisp/i2c/atomisp-gc0310.c
@@ -584,8 +584,6 @@ static void gc0310_remove(struct i2c_client *client)
struct v4l2_subdev *sd = i2c_get_clientdata(client);
struct gc0310_device *dev = to_gc0310_sensor(sd);
- dev_dbg(&client->dev, "gc0310_remove...\n");
-
v4l2_async_unregister_subdev(sd);
media_entity_cleanup(&dev->sd.entity);
v4l2_ctrl_handler_free(&dev->ctrls.handler);
--
2.34.1
next reply other threads:[~2025-06-19 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 8:44 Thomas Andreatta [this message]
2025-06-19 8:44 ` [PATCH 2/4 " Thomas Andreatta
2025-07-06 15:01 ` Hans de Goede
2025-06-19 8:44 ` [PATCH 3/4 V2] Staging: media: atomisp: i2c: struct definition style Thomas Andreatta
2025-07-06 15:01 ` Hans de Goede
2025-06-19 8:44 ` [PATCH 4/4 " Thomas Andreatta
2025-07-06 15:01 ` Hans de Goede
2025-07-06 14:56 ` [PATCH 1/4 V2] Staging: media: atomisp: i2c: removed redundand debug message Hans de Goede
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=20250619084420.146151-1-thomas.andreatta2000@gmail.com \
--to=thomasandreatta2000@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=thomas.andreatta2000@gmail.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®