From: Umang Jain <umang.jain@ideasonboard.com>
To: linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Dan Carpenter <error27@gmail.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Umang Jain <umang.jain@ideasonboard.com>
Subject: [PATCH v1 0/4] staging: vc04: Drop custom logging based on printk
Date: Thu, 19 Oct 2023 13:51:43 +0530 [thread overview]
Message-ID: <20231019082147.384723-1-umang.jain@ideasonboard.com> (raw)
Hello,
This series address the discussion on [1], i.e. removing the printk
based logging mechanism and migrate it use dynamic debug.
Patch 1/4 targets migration of vchiq_log_error().
Patch 2/4 targets migration of vchiq_log_warning().
... and so on.
This series does not touch debugfs entries which are:
DEBUG_INITIALISE, DEBUG_TRACE, DEBUG_VALUE and DEBUG_COUNT. As far as I
understand from the previous discussions, those too should be moved
to use dynamic debug as well (but is not part of this series yet), as
I found there are more moving parts involved. I will build a series on
top of this one, to move the debugfs entries to dynamic debug and remove
all custom logging remanants (like VCHIQ_LOG_* macros, *_log_levels externs)
because they do still tie into vchiq_debugfs.c.
[1] https://lore.kernel.org/linux-media/20230913185528.770634-1-umang.jain@ideasonboard.com/
Umang Jain (4):
staging: vc04: Convert vchiq_log_error() to use dynamic debug
staging: vc04: Convert vchiq_log_warning() to use dynamic debug
staging: vc04: Convert(and rename) vchiq_log_info() to use dynamic
debug
staging: vc04: Convert vchiq_log_trace() to use dynamic debug
.../interface/vchiq_arm/vchiq_arm.c | 143 ++++----
.../interface/vchiq_arm/vchiq_connected.c | 2 +-
.../interface/vchiq_arm/vchiq_core.c | 329 +++++++++---------
.../interface/vchiq_arm/vchiq_core.h | 53 ++-
.../interface/vchiq_arm/vchiq_dev.c | 59 ++--
5 files changed, 307 insertions(+), 279 deletions(-)
--
2.40.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-10-19 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 8:21 Umang Jain [this message]
2023-10-19 8:21 ` [PATCH v1 1/4] staging: vc04: Convert vchiq_log_error() to use dynamic debug Umang Jain
2023-10-19 13:32 ` Kieran Bingham
2023-10-21 9:59 ` Greg Kroah-Hartman
2023-10-19 8:21 ` [PATCH v1 2/4] staging: vc04: Convert vchiq_log_warning() " Umang Jain
2023-10-19 13:50 ` Kieran Bingham
2023-10-19 8:21 ` [PATCH v1 3/4] staging: vc04: Convert(and rename) vchiq_log_info() " Umang Jain
2023-10-19 8:21 ` [PATCH v1 4/4] staging: vc04: Convert vchiq_log_trace() " Umang Jain
2023-10-19 13:56 ` Kieran Bingham
2023-10-19 13:58 ` [PATCH v1 0/4] staging: vc04: Drop custom logging based on printk 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=20231019082147.384723-1-umang.jain@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@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-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