From: Markus Elfring <Markus.Elfring@web.de>
To: Qiushi Wu <wu000273@umn.edu>, netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
oss-drivers@netronome.com, Kangjie Lu <kjlu@umn.edu>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [v3] nfp: abm: Fix incomplete release of system resources in nfp_abm_vnic_set_mac()
Date: Tue, 5 May 2020 07:48:01 +0200 [thread overview]
Message-ID: <6f0e483f-95d8-e30b-6688-e7c3fa6051c4@web.de> (raw)
In-Reply-To: <CAMV6ehE=GXooHwG1TQ-LZqpepceAudX=P63o139UgKG7TMRxwQ@mail.gmail.com>
> Thanks for your feedback, and yes, I'd like to further adjust the description details
> to make the patch more clear and better.
Thanks for such a positive response.
> But because Jakub seems to prefer v1, so I'm somehow confused
Such a view can be reasonable.
The change acceptance varies between involved contributors.
> if I should submit a new version based on v1
Such a choice depends also on your willingness to clarify and improve
the software situation by better commit messages.
> or based on the version that has an addition of a jump target?
I propose that you can offer patch series with two update steps (for example)
according to the affected function implementation.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=47cf1b422e6093aee2a3e55d5e162112a2c69870#n102
1. Add a missing function call for the completion of the desired resource clean-up.
2. Adjust a bit of exception handling code so that it can be better reused
at the end of this function.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=47cf1b422e6093aee2a3e55d5e162112a2c69870#n450
I am curious if you are going to answer (my) previous questions and suggestions
(in constructive ways).
Regards,
Markus
next prev parent reply other threads:[~2020-05-05 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 20:49 [PATCH v3] nfp: abm: Fix incomplete release of system resources in nfp_abm_vnic_set_mac() wu000273
2020-05-04 6:01 ` Markus Elfring
2020-05-04 7:34 ` Markus Elfring
2020-05-04 17:03 ` Jakub Kicinski
[not found] ` <CAMV6ehFC=efyD81rtNRcWW9gbiD4t6z4G2TkLk7WqLS+Qg9X-Q@mail.gmail.com>
2020-05-04 20:13 ` [v3] " Markus Elfring
[not found] ` <CAMV6ehE=GXooHwG1TQ-LZqpepceAudX=P63o139UgKG7TMRxwQ@mail.gmail.com>
2020-05-05 5:48 ` Markus Elfring [this message]
[not found] ` <CAMV6ehEP-X+5bXj6VXMpZCPkr6YZWsB0Z_sTBxFxNpwa6D0Z0Q@mail.gmail.com>
2020-05-05 8:26 ` Markus Elfring
[not found] ` <CAMV6ehE9YRxakbP9ahXkiZEPut8E3qYsN0cxiLqCWasfvLAWFw@mail.gmail.com>
2020-05-05 20:17 ` Markus Elfring
[not found] ` <CAMV6ehFCcSZtqpxonfbp6i_v5zzmnLJ9Gncx=5Y36R35wqTtDw@mail.gmail.com>
2020-05-06 6:12 ` Markus Elfring
[not found] ` <CAK8KejrEuumVxdbBmuHbhjXQa7KH_jP-XLmAHjp1+AC7DUa9WQ@mail.gmail.com>
2020-05-07 7:23 ` [v3] nfp: abm: University research groups? Markus Elfring
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=6f0e483f-95d8-e30b-6688-e7c3fa6051c4@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=kjlu@umn.edu \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=wu000273@umn.edu \
/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).