From: Markus Elfring <Markus.Elfring@web.de>
To: Dejin Zheng <zhengdejin5@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Brian Norris <briannorris@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Yan-Hsuan Chuang <yhchuang@realtek.com>
Subject: Re: [PATCH] net: rtw88: fix an issue about leak system resources
Date: Mon, 4 May 2020 17:00:40 +0200 [thread overview]
Message-ID: <882eacd1-1cbf-6aef-06c5-3ed6d402c0f5@web.de> (raw)
In-Reply-To: <20200504144206.GA5409@nuc8i5>
>>> the related system resources were not released when pci_iomap() return
>>> error in the rtw_pci_io_mapping() function. add pci_release_regions() to
>>> fix it.
>>
>> How do you think about a wording variant like the following?
>>
>> Subject:
>> [PATCH v2] net: rtw88: Complete exception handling in rtw_pci_io_mapping()
>>
>> Change description:
>> A call of the function “pci_request_regions” can fail here.
>> The corresponding system resources were not released then.
>> Thus add a call of the function “pci_release_regions”.
>>
>>
> Markus, I think my commit comments is a sufficiently clear description
> for this patch.
I got an other impression for specific aspects.
> Someone has told me not to send commit comments again and again
> when it is enough clear.
My patch review tries should give you hints where I noticed wording weaknesses.
The corresponding change tolerance can vary by involved contributors.
> Because it only wastes the precious time of the maintainer
> and very very little help for patch improvement.
I hope that also your commit messages will improve.
> BTW, In the past week, you asked me to change the commit comments in my
> 6 patches like this one. Let me return to the essence of patch, point
> out the code problems and better solutions will be more popular.
I would appreciate if various update suggestions would become nicer somehow.
Regards,
Markus
next prev parent reply other threads:[~2020-05-04 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:51 Markus Elfring
[not found] ` <20200504144206.GA5409@nuc8i5>
2020-05-04 15:00 ` Markus Elfring [this message]
2020-05-04 17:03 ` Brian Norris
2020-05-04 17:19 ` Markus Elfring
2020-05-04 17:19 ` Markus Elfring
2020-05-05 0:59 ` [PATCH] " Dejin Zheng
2020-05-05 6:15 ` Markus Elfring
2020-05-05 8:52 ` [PATCH] " Andy Shevchenko
2020-05-05 9:03 ` net: rtw88: Fix an issue about leaking " 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=882eacd1-1cbf-6aef-06c5-3ed6d402c0f5@web.de \
--to=markus.elfring@web.de \
--cc=andy.shevchenko@gmail.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=yhchuang@realtek.com \
--cc=zhengdejin5@gmail.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
all inboxes | Powered by JetHome®