netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: alejandro.lucero-palau@amd.com
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, habetsm.xilinx@gmail.com,
	ecree.xilinx@gmail.com, linux-doc@vger.kernel.org,
	corbet@lwn.net, jiri@nvidia.com
Subject: Re: [PATCH v7 net-next 2/8] sfc: add devlink info support for ef100
Date: Tue, 14 Feb 2023 09:39:42 +0200	[thread overview]
Message-ID: <Y+s6vrDLkpLRwtx3@unreal> (raw)
In-Reply-To: <20230213183428.10734-3-alejandro.lucero-palau@amd.com>

On Mon, Feb 13, 2023 at 06:34:22PM +0000, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
> 
> Add devlink info support for ef100. The information reported is obtained
> through the MCDI interface with the specific meaning defined in new
> documentation file.
> 
> Signed-off-by: Alejandro Lucero <alejandro.lucero-palau@amd.com>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> ---
>  Documentation/networking/devlink/index.rst |   1 +
>  Documentation/networking/devlink/sfc.rst   |  57 +++
>  MAINTAINERS                                |   1 +
>  drivers/net/ethernet/sfc/efx_devlink.c     | 459 +++++++++++++++++++++
>  drivers/net/ethernet/sfc/efx_devlink.h     |  17 +
>  drivers/net/ethernet/sfc/mcdi.c            |  72 ++++
>  drivers/net/ethernet/sfc/mcdi.h            |   3 +
>  7 files changed, 610 insertions(+)
>  create mode 100644 Documentation/networking/devlink/sfc.rst

<...>

> +static void efx_devlink_info_running_v2(struct efx_nic *efx,
> +					struct devlink_info_req *req,
> +					unsigned int flags, efx_dword_t *outbuf)
> +{
> +	char buf[EFX_MAX_VERSION_INFO_LEN];
> +	union {
> +		const __le32 *dwords;
> +		const __le16 *words;
> +		const char *str;
> +	} ver;
> +	struct rtc_time build_date;
> +	unsigned int build_id;
> +	size_t offset;
> +#ifdef CONFIG_RTC_LIB
> +	u64 tstamp;
> +#endif

If you are going to resubmit the series.

Documentation/process/coding-style.rst
  1140 21) Conditional Compilation
  1141 ---------------------------
....
  1156 If you have a function or variable which may potentially go unused in a
  1157 particular configuration, and the compiler would warn about its definition
  1158 going unused, mark the definition as __maybe_unused rather than wrapping it in
  1159 a preprocessor conditional.  (However, if a function or variable *always* goes
  1160 unused, delete it.)

Thanks

  reply	other threads:[~2023-02-14  7:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 18:34 [PATCH v7 net-next 0/8] sfc: devlink support for ef100 alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 1/8] sfc: add " alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 2/8] sfc: add devlink info " alejandro.lucero-palau
2023-02-14  7:39   ` Leon Romanovsky [this message]
2023-02-14 15:28     ` Edward Cree
2023-02-14 16:56       ` Alexander Lobakin
2023-02-15  8:43         ` Lucero Palau, Alejandro
2023-02-15 12:22           ` Leon Romanovsky
2023-02-15 17:07             ` Alexander Lobakin
2023-02-14  8:51   ` Martin Habets
2023-02-13 18:34 ` [PATCH v7 net-next 3/8] sfc: enumerate mports in ef100 alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 4/8] sfc: add mport lookup based on driver's mport data alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 5/8] sfc: add devlink port support for ef100 alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 6/8] sfc: obtain device mac address based on firmware handle " alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 7/8] sfc: add support for devlink port_function_hw_addr_get in ef100 alejandro.lucero-palau
2023-02-13 18:34 ` [PATCH v7 net-next 8/8] sfc: add support for devlink port_function_hw_addr_set " alejandro.lucero-palau

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=Y+s6vrDLkpLRwtx3@unreal \
    --to=leon@kernel.org \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=habetsm.xilinx@gmail.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).