> -----Original Message----- > From: Igor Russkikh <[email protected]> > Sent: Sunday, February 21, 2021 4:47 PM > To: [email protected] > Cc: Rasesh Mody <[email protected]>; Devendra Singh Rawat > <[email protected]>; Igor Russkikh <[email protected]>; > [email protected] > Subject: [PATCH 1/2] qede: reduce trace verbosity level > > On some hardware units it was found this trace is flooding the output, making > any dpdk interactive usage kind of problematic. > > It is only informational, without any consequences handling, so reducing it to > verbose from explicit notice level. > > CC: [email protected] > Signed-off-by: Igor Russkikh <[email protected]> > --- > drivers/net/qede/base/ecore_int.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/net/qede/base/ecore_int.c > b/drivers/net/qede/base/ecore_int.c > index 4207b1853..2c4aac941 100644 > --- a/drivers/net/qede/base/ecore_int.c > +++ b/drivers/net/qede/base/ecore_int.c > @@ -928,7 +928,7 @@ static void ecore_int_attn_print(struct ecore_hwfn > *p_hwfn, > bool b_clear) > { > /* @DPDK */ > - DP_NOTICE(p_hwfn->p_dev, false, "[block_id %d type %d]\n", id, > type); > + DP_VERBOSE(p_hwfn, ECORE_MSG_INTR, "[block_id %d type %d]\n", > id, > +type); > } > > /** > -- > 2.25.1
ACK, Acked-by: Devendra Singh Rawat <[email protected]> Thanks, Devendra
