From: Umang Jain <umang.jain@ideasonboard.com>
To: linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Adrien Thierry <athierry@redhat.com>,
Dan Carpenter <error27@gmail.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Umang Jain <umang.jain@ideasonboard.com>
Subject: [RFC PATCH 0/4] Drop custom logging
Date: Wed, 18 Jan 2023 17:28:06 +0530 [thread overview]
Message-ID: <20230118115810.21979-1-umang.jain@ideasonboard.com> (raw)
Drop custom logging from the vchiq interface.
Mostly of them are replaced with dev_dbg and friends
and/or pr_info and friends.
The debugfs log levels (in 4/4) are mapped to kernel
logs levels (coming from include/linux/kern_levels.h)
Would like some thoughts on it as I am not sure (hence
marking this is RFC)
From drivers/staging/vc04_services/interface/TODO:
"""
* Cleanup logging mechanism
The driver should probably be using the standard kernel logging mechanisms
such as dev_info, dev_dbg, and friends.
"""
Umang Jain (4):
staging: vc04_services: vchiq_core: Drop custom logging
staging: vc04_services: vchiq_arm: Drop custom logging
staging: vc04_services: Drop custom logging
staging: vc04_services: Drop remnants of custom logging
.../interface/vchiq_arm/vchiq_arm.c | 151 +++---
.../interface/vchiq_arm/vchiq_connected.c | 5 +-
.../interface/vchiq_arm/vchiq_core.c | 479 ++++++++----------
.../interface/vchiq_arm/vchiq_core.h | 39 --
.../interface/vchiq_arm/vchiq_debugfs.c | 26 +-
.../interface/vchiq_arm/vchiq_dev.c | 78 ++-
6 files changed, 329 insertions(+), 449 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-18 12:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 11:58 Umang Jain [this message]
2023-01-18 11:58 ` [RFC PATCH 1/4] staging: vc04_services: vchiq_core: Drop custom logging Umang Jain
2023-01-18 17:29 ` Stefan Wahren
2023-01-19 14:32 ` Dan Carpenter
2023-01-18 11:58 ` [RFC PATCH 2/4] staging: vc04_services: vchiq_arm: " Umang Jain
2023-01-18 11:58 ` [RFC PATCH 3/4] staging: vc04_services: " Umang Jain
2023-01-18 11:58 ` [RFC PATCH 4/4] staging: vc04_services: Drop remnants of " Umang Jain
2023-01-18 18:10 ` Stefan Wahren
2023-01-18 17:54 ` [RFC PATCH 0/4] Drop " Stefan Wahren
2023-01-19 5:11 ` Dan Carpenter
2023-01-19 13:31 ` Phil Elwell
2023-01-19 13:37 ` Greg Kroah-Hartman
2023-01-19 13:47 ` Phil Elwell
2023-01-19 14:25 ` Dan Carpenter
2023-01-19 14:31 ` Phil Elwell
2023-01-19 14:37 ` Dan Carpenter
2023-01-19 14:39 ` Phil Elwell
2023-01-20 0:53 ` Laurent Pinchart
2023-01-20 1:00 ` Laurent Pinchart
2023-01-23 12:04 ` Dan Carpenter
2023-01-19 9:34 ` Greg Kroah-Hartman
2023-01-22 14:21 ` Stefan Wahren
2023-01-22 16:26 ` Kieran Bingham
2023-01-22 18:07 ` Stefan Wahren
2023-01-23 16:54 ` Kieran Bingham
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=20230118115810.21979-1-umang.jain@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=athierry@redhat.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).