From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/1] ice: compact the file ice_nvm.c
Date: Mon, 18 Oct 2021 22:22:28 +0800 [thread overview]
Message-ID: <2b0dbaf8-1033-b1a3-8976-83a785fbe682@linux.dev> (raw)
In-Reply-To: <10c80bab-db74-b567-505c-95d74763248f@molgen.mpg.de>
? 2021/10/18 22:05, Paul Menzel ??:
> Dear Yanjun,
>
>
> Am 18.10.21 um 16:00 schrieb Yanjun Zhu:
>
>> ? 2021/10/18 21:44, Paul Menzel ??:
>
>>> Am 18.10.21 um 15:17 schrieb yanjun.zhu at linux.dev:
>>>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>>>>
>>>> The function ice_aq_nvm_update_empr is not used, so remove it.
>>>
>>> Thank you for the patch. Could you please make the commit message
>>> summary more descriptive? Maybe:
>>>
>>>> ice: Remove unused `ice_aq_nvm_update_empr()`
>>>
>>> If you find out, what commit removed the usage, that would be also
>>> good to document, but it?s not that important.
>>
>> Thanks for your suggestion.
>>
>> IMO, removing the unused function is one method of compact file.
>>
>> I agree with you that the commit message summary is not important.
>
> Sorry, you misunderstood me. The commit message summary is my opinion
> very important, as it?s what shown in `git log --oneline`, and in this
> case everybody has to read the full commit message to know what the
> commit actually as *compact* is not conveying this meaning and is
> ambiguous.
>
> Not as important is finding the commit removing the last user, and
> adding a Fixes tag with it.
Got it.
>
>> If someone finds more important problem in this commit, I will resend
>> the
>>
>> patch and change the commit message summary based on your suggestion.
>
> It?d be great, if you sent an improved version.
I will resend the latest version.
Zhu Yanjun
>
>
> Kind regards,
>
> Paul
prev parent reply other threads:[~2021-10-18 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 13:17 [Intel-wired-lan] [PATCH 1/1] ice: compact the file ice_nvm.c yanjun.zhu
2021-10-18 13:44 ` Paul Menzel
2021-10-18 14:00 ` Yanjun Zhu
2021-10-18 14:05 ` Paul Menzel
2021-10-18 14:22 ` Yanjun Zhu [this message]
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=2b0dbaf8-1033-b1a3-8976-83a785fbe682@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=intel-wired-lan@osuosl.org \
/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