[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97e4fc5a-85d2-3b46-12c3-7e893a3305d8@intel.com>
Date: Wed, 26 Apr 2023 17:24:58 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: "Drewek, Wojciech" <wojciech.drewek@...el.com>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Ertman, David M" <david.m.ertman@...el.com>,
"michal.swiatkowski@...ux.intel.com"
<michal.swiatkowski@...ux.intel.com>,
"marcin.szycik@...ux.intel.com" <marcin.szycik@...ux.intel.com>,
"Chmielewski, Pawel" <pawel.chmielewski@...el.com>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>
Subject: Re: [PATCH net-next 06/12] ice: Add guard rule when creating FDB in
switchdev
From: Wojciech Drewek <wojciech.drewek@...el.com>
Date: Wed, 26 Apr 2023 11:50:56 +0200
>
>
>> -----Original Message-----
>> From: Drewek, Wojciech
>> Sent: wtorek, 25 kwietnia 2023 11:18
>> To: Lobakin, Aleksander <aleksander.lobakin@...el.com>
[...]
>>> guard_rule = ice_eswitch_...
>>> err = PTR_ERR(guard_rule);
>>> if (err) {
>>> ...
>>>
>>
>> I like it, less ptr <-> macros
>
> Actually it won't work, PTR_ERR would not convert pointer to 0 in case of success.
Ooops, PTR_ERR_OR_ZERO() then? I forgot there are several macros for
different cases =\
>
>>
>>>> + dev_err(dev, "Failed to create eswitch bridge %sgress guard rule, err: %d\n",
>>>> + port_type == ICE_ESWITCH_BR_UPLINK_PORT ? "e" : "in",
>>>> + err);
>>>
>>> You still can print it via "%pe" + @guard_rule instead of @err :p (same
>>> with @fwd_rule above)
[...]
Thanks,
Olek
Powered by blists - more mailing lists