[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8lS5eBliYw5EHBb@kadam>
Date: Thu, 19 Jan 2023 17:25:41 +0300
From: Dan Carpenter <error27@...il.com>
To: Phil Elwell <phil@...pberrypi.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stefan Wahren <stefan.wahren@...e.com>,
Umang Jain <umang.jain@...asonboard.com>,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org,
Florian Fainelli <f.fainelli@...il.com>,
Adrien Thierry <athierry@...hat.com>,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Kieran Bingham <kieran.bingham@...asonboard.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/4] Drop custom logging
On Thu, Jan 19, 2023 at 01:47:44PM +0000, Phil Elwell wrote:
> > > I understand the desire to remove the custom logging. I don't welcome
> > > the loss of flexibility that comes with such a strategy
> >
> > What "loss of flexibility"? You now have access to the full dynamic
> > debugging facilities that all of the rest of the kernel has. What is
> > lacking?
>
> Perhaps I've missed something, either in this patch set or the kernel
> as a whole, but how is one supposed to set different logging levels on
> different facilities within a driver/module, or even for the module as
> a whole?
Yeah. You will be still able to do that and more besides after the
transition. Cleaning this up makes the code better in every way.
Documentation/admin-guide/dynamic-debug-howto.rst
regards,
dan carpenter
Powered by blists - more mailing lists