[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230118115810.21979-1-umang.jain@ideasonboard.com>
Date: Wed, 18 Jan 2023 17:28:06 +0530
From: Umang Jain <umang.jain@...asonboard.com>
To: linux-staging@...ts.linux.dev,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Stefan Wahren <stefan.wahren@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Florian Fainelli <f.fainelli@...il.com>,
Adrien Thierry <athierry@...hat.com>,
Dan Carpenter <error27@...il.com>,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Kieran Bingham <kieran.bingham@...asonboard.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Umang Jain <umang.jain@...asonboard.com>
Subject: [RFC PATCH 0/4] Drop custom logging
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
Powered by blists - more mailing lists