From: "G, GurucharanX" <gurucharanx.g@intel.com>
To: "Sokolowski, Jan" <jan.sokolowski@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v5 5/5] i40e: use ERR_PTR error print in i40e messages
Date: Fri, 3 Feb 2023 07:38:14 +0000 [thread overview]
Message-ID: <BYAPR11MB33679EFB5CB6FE5018FD746BFCD79@BYAPR11MB3367.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230109141120.3197817-6-jan.sokolowski@intel.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Jan Sokolowski
> Sent: Monday, January 9, 2023 7:41 PM
> To: intel-wired-lan@lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH net-next v5 5/5] i40e: use ERR_PTR error
> print in i40e messages
>
> In i40e_status removal patches, i40e_status conversion to strings was
> removed in order to easily refactor the code to use standard errornums. This
> however made it more difficult for read error logs.
>
> Use %pe formatter to print error messages in human-readable format.
>
> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_client.c | 8 +-
> drivers/net/ethernet/intel/i40e/i40e_dcb_nl.c | 16 +-
> .../net/ethernet/intel/i40e/i40e_ethtool.c | 40 +--
> drivers/net/ethernet/intel/i40e/i40e_main.c | 298 +++++++++---------
> drivers/net/ethernet/intel/i40e/i40e_nvm.c | 4 +-
> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 28 +-
> 6 files changed, 197 insertions(+), 197 deletions(-)
>
Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-02-03 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:11 [Intel-wired-lan] [PATCH net-next v5 0/5] i40e_status removal series Jan Sokolowski
2023-01-09 14:11 ` [Intel-wired-lan] [PATCH net-next v5 1/5] i40e: Remove unused i40e status codes Jan Sokolowski
2023-02-03 7:31 ` G, GurucharanX
2023-01-09 14:11 ` [Intel-wired-lan] [PATCH net-next v5 2/5] i40e: Remove string printing for i40e_status Jan Sokolowski
2023-02-03 7:32 ` G, GurucharanX
2023-01-09 14:11 ` [Intel-wired-lan] [PATCH net-next v5 3/5] i40e: use int " Jan Sokolowski
2023-02-03 7:35 ` G, GurucharanX
2023-01-09 14:11 ` [Intel-wired-lan] [PATCH net-next v5 4/5] i40e: remove i40e_status Jan Sokolowski
2023-02-03 7:37 ` G, GurucharanX
2023-01-09 14:11 ` [Intel-wired-lan] [PATCH net-next v5 5/5] i40e: use ERR_PTR error print in i40e messages Jan Sokolowski
2023-02-03 7:38 ` G, GurucharanX [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=BYAPR11MB33679EFB5CB6FE5018FD746BFCD79@BYAPR11MB3367.namprd11.prod.outlook.com \
--to=gurucharanx.g@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jan.sokolowski@intel.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