From: Simon Horman <horms@kernel.org>
To: David Thompson <davthompson@nvidia.com>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
"u.kleine-koenig@baylibre.com" <u.kleine-koenig@baylibre.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v1] mlxbf_gige: emit messages during open and probe failures
Date: Tue, 1 Jul 2025 13:51:50 +0100 [thread overview]
Message-ID: <20250701125150.GR41770@horms.kernel.org> (raw)
In-Reply-To: <PH7PR12MB5902AE4A0311CA4B47F02F8FC741A@PH7PR12MB5902.namprd12.prod.outlook.com>
On Tue, Jul 01, 2025 at 12:44:14AM +0000, David Thompson wrote:
> > -----Original Message-----
> > From: Simon Horman <horms@kernel.org>
> > Sent: Monday, June 16, 2025 3:18 PM
> > To: Alexander Lobakin <aleksander.lobakin@intel.com>
> > Cc: David Thompson <davthompson@nvidia.com>; andrew+netdev@lunn.ch;
> > davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
> > pabeni@redhat.com; Asmaa Mnebhi <asmaa@nvidia.com>; u.kleine-
> > koenig@baylibre.com; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH net-next v1] mlxbf_gige: emit messages during open and
> > probe failures
> >
> > On Mon, Jun 16, 2025 at 04:06:49PM +0200, Alexander Lobakin wrote:
> > > From: Simon Horman <horms@kernel.org>
> > > Date: Mon, 16 Jun 2025 14:57:10 +0100
> > >
> > > > On Fri, Jun 13, 2025 at 05:42:28PM +0000, David Thompson wrote:
> > > >> The open() and probe() functions of the mlxbf_gige driver check for
> > > >> errors during initialization, but do not provide details regarding
> > > >> the errors. The mlxbf_gige driver should provide error details in
> > > >> the kernel log, noting what step of initialization failed.
> > > >>
> > > >> Signed-off-by: David Thompson <davthompson@nvidia.com>
> > > >
> > > > Hi David,
> > > >
> > > > I do have some reservations about the value of printing out raw err
> > > > values. But I also see that the logging added by this patch is
> > > > consistent with existing code in this driver.
> > > > So in that context I agree this is appropriate.
> > > >
> > > > Reviewed-by: Simon Horman <horms@kernel.org>
> > >
> > > I still think it's better to encourage people to use %pe for printing
> > > error codes. The already existing messages could be improved later,
> > > but then at least no new places would sneak in.
> >
> > Thanks, I agree that is reasonable.
> > And as a bonus the patch-set could update existing messages.
> >
> > David, could you consider making this so?
>
> Sorry for late response.
>
> Yes, will look into updating this patch to use %pe
>
> Thanks for the feedback.
Thanks, much appreciated.
prev parent reply other threads:[~2025-07-01 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 17:42 David Thompson
2025-06-16 13:57 ` Simon Horman
2025-06-16 14:06 ` Alexander Lobakin
2025-06-16 19:17 ` Simon Horman
2025-07-01 0:44 ` David Thompson
2025-07-01 12:51 ` Simon Horman [this message]
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=20250701125150.GR41770@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@baylibre.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®