From: Nikolay Aleksandrov <razor@blackwall.org>
To: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>,
netdev@vger.kernel.org
Cc: outreachy@lists.linux.dev, roopa@nvidia.com, jdenham@redhat.com,
sbrivio@redhat.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, vladimir.oltean@nxp.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
shshaikh@marvell.com, manishc@marvell.com,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, GR-Linux-NIC-Dev@marvell.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next v3 1/2] rtnetlink: add extack support in fdb del handlers
Date: Mon, 25 Apr 2022 00:52:39 +0300 [thread overview]
Message-ID: <0f1e1250-920a-c7d1-900c-98ef3e0456d8@blackwall.org> (raw)
In-Reply-To: <3bcb2d3d-8b8b-8a8f-1285-7277394b4e6b@gmail.com>
On 4/25/22 00:09, Alaa Mohamed wrote:
>
> On ٢٤/٤/٢٠٢٢ ٢١:٥٥, Nikolay Aleksandrov wrote:
>> On 24/04/2022 22:49, Alaa Mohamed wrote:
>>> On ٢٤/٤/٢٠٢٢ ٢١:٠٢, Nikolay Aleksandrov wrote:
>>>> On 24/04/2022 15:09, Alaa Mohamed wrote:
>>>>> Add extack support to .ndo_fdb_del in netdevice.h and
>>>>> all related methods.
>>>>>
>>>>> Signed-off-by: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
>>>>> ---
>>>>> changes in V3:
>>>>> fix errors reported by checkpatch.pl
>>>>> ---
>>>>> drivers/net/ethernet/intel/ice/ice_main.c | 4 ++--
>>>>> drivers/net/ethernet/mscc/ocelot_net.c | 4 ++--
>>>>> drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c | 2 +-
>>>>> drivers/net/macvlan.c | 2 +-
>>>>> drivers/net/vxlan/vxlan_core.c | 2 +-
>>>>> include/linux/netdevice.h | 2 +-
>>>>> net/bridge/br_fdb.c | 2 +-
>>>>> net/bridge/br_private.h | 2 +-
>>>>> net/core/rtnetlink.c | 4 ++--
>>>>> 9 files changed, 12 insertions(+), 12 deletions(-)
>>>>>
>>>>> diff --git a/drivers/net/ethernet/intel/ice/ice_main.c
>>>>> b/drivers/net/ethernet/intel/ice/ice_main.c
>>>>> index d768925785ca..7b55d8d94803 100644
>>>>> --- a/drivers/net/ethernet/intel/ice/ice_main.c
>>>>> +++ b/drivers/net/ethernet/intel/ice/ice_main.c
>>>>> @@ -5678,10 +5678,10 @@ ice_fdb_add(struct ndmsg *ndm, struct
>>>>> nlattr __always_unused *tb[],
>>>>> static int
>>>>> ice_fdb_del(struct ndmsg *ndm, __always_unused struct nlattr *tb[],
>>>>> struct net_device *dev, const unsigned char *addr,
>>>>> - __always_unused u16 vid)
>>>>> + __always_unused u16 vid, struct netlink_ext_ack *extack)
>>>>> {
>>>>> int err;
>>>>> -
>>>>> +
>>>> What's changed here?
>>> In the previous version, I removed the blank line after "int err;"
>>> and you said I shouldn't so I added blank line.
>>>
>> Yeah, my question is are you fixing a dos ending or something else?
>> The blank line is already there, what's wrong with it?
> No, I didn't.
>>
>> The point is it's not nice to mix style fixes and other changes, more so
>> if nothing is mentioned in the commit message.
> Got it, So, what should I do to fix it?
Don't change that line? I mean I'm even surprised this made it in the
patch. As I mentioned above, there is already a new line there so I'm
not sure how you're removing it and adding it again. :)
Cheers,
Nik
next prev parent reply other threads:[~2022-04-24 21:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 12:09 [PATCH net-next v3 0/2] propagate extack to vxlan_fdb_delete Alaa Mohamed
2022-04-24 12:09 ` [PATCH net-next v3 1/2] rtnetlink: add extack support in fdb del handlers Alaa Mohamed
2022-04-24 19:02 ` Nikolay Aleksandrov
2022-04-24 19:49 ` Alaa Mohamed
2022-04-24 19:55 ` Nikolay Aleksandrov
2022-04-24 21:09 ` Alaa Mohamed
2022-04-24 21:52 ` Nikolay Aleksandrov [this message]
2022-04-25 11:47 ` Alaa Mohamed
2022-04-25 6:11 ` Julia Lawall
2022-04-25 11:51 ` Alaa Mohamed
2022-04-25 6:12 ` Julia Lawall
2022-04-24 12:09 ` [PATCH net-next v3 2/2] net: vxlan: vxlan_core.c: Add extack support to vxlan_fdb_delete Alaa Mohamed
2022-04-24 16:15 ` Julia Lawall
2022-04-24 18:52 ` Alaa Mohamed
2022-04-24 18:56 ` Julia Lawall
2022-04-24 18:59 ` Alaa Mohamed
2022-04-24 19:03 ` Nikolay Aleksandrov
2022-04-24 19:20 ` Alaa Mohamed
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=0f1e1250-920a-c7d1-900c-98ef3e0456d8@blackwall.org \
--to=razor@blackwall.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bridge@lists.linux-foundation.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdenham@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.com \
--cc=sbrivio@redhat.com \
--cc=shshaikh@marvell.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).