From: Jakub Kicinski <kuba@kernel.org>
To: Lee Trager <lee@trager.us>
Cc: Alexander Duyck <alexanderduyck@fb.com>,
kernel-team@meta.com, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Sanman Pradhan <sanmanpradhan@meta.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Mohsin Bashir <mohsin.bashr@gmail.com>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] eth: fbnic: Add devlink dev flash support
Date: Mon, 11 Nov 2024 19:19:31 -0800 [thread overview]
Message-ID: <20241111191931.284b1be4@kernel.org> (raw)
In-Reply-To: <20241111043058.1251632-3-lee@trager.us>
Please drop Al Viro from the CC (!?) and CC the maintainer of the pldm
library (Jake).
On Sun, 10 Nov 2024 20:28:42 -0800 Lee Trager wrote:
> +/**
> + * fbnic_send_package_data - Send record package data to firmware
> + * @context: PLDM FW update structure
> + * @data: pointer to the package data
> + * @length: length of the package data
> + *
> + * Send a copy of the package data associated with the PLDM record matching
> + * this device to the firmware.
> + *
> + * Return: zero on success
> + * negative error code on failure
> + */
can we drop these kdocs please? In the bast case they just repeat
the function name ("send package data") 3 times, in the worst case they
are misleading. This function sends absolutely nothing to the firmware.
> +static int fbnic_send_package_data(struct pldmfw *context, const u8 *data,
> + u16 length)
> +{
> + struct device *dev = context->dev;
> +
> + /* Temp placeholder required by devlink */
Do you mean that the pldm lib requires this callback to exist?
If yes then make it not require it if it's not necessary?
> + dev_info(dev,
> + "Sending %u bytes of PLDM record package data to firmware\n",
> + length);
Please drop all the dev_*() prints. If something is important enough to
be reported it should be reported via the devlink info channel, to the
user. Not to system logs.
> + return 0;
> +}
--
pw-bot: cr
next prev parent reply other threads:[~2024-11-12 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 4:28 [PATCH net-next v3 0/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-11-11 4:28 ` [PATCH net-next v3 1/2] eth: fbnic: Add mailbox support for PLDM updates Lee Trager
2024-11-11 4:28 ` [PATCH net-next v3 2/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-11-12 3:19 ` Jakub Kicinski [this message]
2024-11-12 17:42 ` Simon Horman
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=20241111191931.284b1be4@kernel.org \
--to=kuba@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kernel-team@meta.com \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sanmanpradhan@meta.com \
--cc=viro@zeniv.linux.org.uk \
/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).