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:00:05 +0800 [thread overview]
Message-ID: <087710e9-2aeb-c070-cebb-82ae9cb5c20e@linux.dev> (raw)
In-Reply-To: <c1903730-9508-1fef-4232-3a5b62f28d7c@molgen.mpg.de>
? 2021/10/18 21:44, Paul Menzel ??:
> Dear Yanjun,
>
>
> 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.
If someone finds more important problem in this commit, I will resend the
patch and change the commit message summary based on your suggestion.
Best Regards.
Zhu Yanjun
>
>
> Kind regards,
>
> Paul
>
>
>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>> ---
>> ? drivers/net/ethernet/intel/ice/ice_nvm.c | 16 ----------------
>> ? drivers/net/ethernet/intel/ice/ice_nvm.h |? 1 -
>> ? 2 files changed, 17 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_nvm.c
>> b/drivers/net/ethernet/intel/ice/ice_nvm.c
>> index fee37a5844cf..bad374bd7ab3 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_nvm.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_nvm.c
>> @@ -1106,22 +1106,6 @@ enum ice_status ice_nvm_write_activate(struct
>> ice_hw *hw, u8 cmd_flags)
>> ????? return ice_aq_send_cmd(hw, &desc, NULL, 0, NULL);
>> ? }
>> ? -/**
>> - * ice_aq_nvm_update_empr
>> - * @hw: pointer to the HW struct
>> - *
>> - * Update empr (0x0709). This command allows SW to
>> - * request an EMPR to activate new FW.
>> - */
>> -enum ice_status ice_aq_nvm_update_empr(struct ice_hw *hw)
>> -{
>> -??? struct ice_aq_desc desc;
>> -
>> -??? ice_fill_dflt_direct_cmd_desc(&desc, ice_aqc_opc_nvm_update_empr);
>> -
>> -??? return ice_aq_send_cmd(hw, &desc, NULL, 0, NULL);
>> -}
>> -
>> ? /* ice_nvm_set_pkg_data
>> ?? * @hw: pointer to the HW struct
>> ?? * @del_pkg_data_flag: If is set then the current pkg_data store by FW
>> diff --git a/drivers/net/ethernet/intel/ice/ice_nvm.h
>> b/drivers/net/ethernet/intel/ice/ice_nvm.h
>> index c6f05f43d593..925225905491 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_nvm.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_nvm.h
>> @@ -39,7 +39,6 @@ enum ice_status
>> ? ice_aq_erase_nvm(struct ice_hw *hw, u16 module_typeid, struct
>> ice_sq_cd *cd);
>> ? enum ice_status ice_nvm_validate_checksum(struct ice_hw *hw);
>> ? enum ice_status ice_nvm_write_activate(struct ice_hw *hw, u8
>> cmd_flags);
>> -enum ice_status ice_aq_nvm_update_empr(struct ice_hw *hw);
>> ? enum ice_status
>> ? ice_nvm_set_pkg_data(struct ice_hw *hw, bool del_pkg_data_flag, u8
>> *data,
>> ?????????????? u16 length, struct ice_sq_cd *cd);
>>
next prev parent reply other threads:[~2021-10-18 14:00 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 [this message]
2021-10-18 14:05 ` Paul Menzel
2021-10-18 14:22 ` Yanjun Zhu
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=087710e9-2aeb-c070-cebb-82ae9cb5c20e@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