[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220412084659.60838d73@kernel.org>
Date: Tue, 12 Apr 2022 08:46:59 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Simon Horman <simon.horman@...igine.com>,
Dylan Muller <dylan.muller@...igine.com>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
oss-drivers@...igine.com
Subject: Re: [PATCH net-next] nfp: update nfp_X logging definitions
On Tue, 12 Apr 2022 17:26:00 +0200 Simon Horman wrote:
> From: Dylan Muller <dylan.muller@...igine.com>
>
> Previously it was not possible to determine which code path was responsible
> for generating a certain message after a call to the nfp_X messaging
> definitions for cases of duplicate strings. We therefore modify nfp_err,
> nfp_warn, nfp_info, nfp_dbg and nfp_printk to print the corresponding file
> and line number where the nfp_X definition is used.
>
> Signed-off-by: Dylan Muller <dylan.muller@...igine.com>
> Signed-off-by: Simon Horman <simon.horman@...igine.com>
Examples? The messages are usually unique. Unless you also print
the kernel version the line numbers are meaningless in real life.
Powered by blists - more mailing lists