netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shannon Nelson <snelson@pensando.io>
To: Jacob Keller <jacob.e.keller@intel.com>, netdev@vger.kernel.org
Cc: Jiri Pirko <jiri@nvidia.com>,
	Michael Chan <michael.chan@broadcom.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Boris Pismenny <borisp@nvidia.com>, Bin Luo <luobin9@huawei.com>,
	Jakub Kicinksi <kuba@kernel.org>
Subject: Re: [net-next v2 PATCH] devlink: move request_firmware out of driver
Date: Wed, 18 Nov 2020 10:55:25 -0800	[thread overview]
Message-ID: <4109cfe1-abb1-9f67-d93b-fee062a5bfbb@pensando.io> (raw)
In-Reply-To: <0371781e-f411-e78e-be6d-971e8989d6ba@intel.com>

On 11/18/20 10:52 AM, Jacob Keller wrote:
> On 11/13/2020 3:48 PM, Shannon Nelson wrote:
>> On 11/13/20 2:45 PM, Jacob Keller wrote:
>>> -int ionic_firmware_update(struct ionic_lif *lif, const char *fw_name,
>>> +int ionic_firmware_update(struct ionic_lif *lif, const struct firmware *fw,
>>>    			  struct netlink_ext_ack *extack)
>>>    {
>>>    	struct ionic_dev *idev = &lif->ionic->idev;
>>> @@ -99,24 +99,15 @@ int ionic_firmware_update(struct ionic_lif *lif, const char *fw_name,
>>>    	struct ionic *ionic = lif->ionic;
>>>    	union ionic_dev_cmd_comp comp;
>>>    	u32 buf_sz, copy_sz, offset;
>>> -	const struct firmware *fw;
>>>    	struct devlink *dl;
>>>    	int next_interval;
>>>    	int err = 0;
>>>    	u8 fw_slot;
>>>    
>>> -	netdev_info(netdev, "Installing firmware %s\n", fw_name);
>>> -
>> I prefer keeping the chatty little bits like this for debug purposes,
>> but if you're going to remove it, then you should remove the matching
>> netdev_info "Firmware update completed" message a few lines before the
>> release_firmware().
>>
>> Aside from that, for the ionic bits:
>> Acked-by: Shannon Nelson <snelson@pensando.io>
>>
>> Thanks,
>> sln
>>
> So the only reason I removed this is because the function no longer has
> access to the fw_name string. I'll change it to just remove the %s
> format string.

Thanks,
sln


      reply	other threads:[~2020-11-18 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 22:45 [net-next v2 PATCH] devlink: move request_firmware out of driver Jacob Keller
2020-11-13 23:48 ` Shannon Nelson
2020-11-18 18:52   ` Jacob Keller
2020-11-18 18:55     ` Shannon Nelson [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=4109cfe1-abb1-9f67-d93b-fee062a5bfbb@pensando.io \
    --to=snelson@pensando.io \
    --cc=borisp@nvidia.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=luobin9@huawei.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.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).