DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
	Shahaf Shuler <shahafs@mellanox.com>
Cc: Ori Kam <orika@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: port kernel definitions for module EEPROM
Date: Tue, 10 Sep 2019 06:11:44 +0000	[thread overview]
Message-ID: <VI1PR05MB3278C1D5E0263B282247F25AD2B60@VI1PR05MB3278.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <d9481d6b5d57c8b8eab4069b3ccff33e060039a4.1568027294.git.dekelp@mellanox.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
> Sent: Monday, September 9, 2019 14:10
> To: Thomas Monjalon <thomas@monjalon.net>; ferruh.yigit@intel.com;
> arybchenko@solarflare.com; Shahaf Shuler <shahafs@mellanox.com>
> Cc: Ori Kam <orika@mellanox.com>; dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] ethdev: port kernel definitions for module
> EEPROM
> 
> This patch copies definitions of maximal data length in module eeprom, from
> include/uapi/linux/ethtool.h.
> 
> These definitions can be used by application to validate data length.
> 
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

> ---
>  lib/librte_ethdev/rte_dev_info.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/librte_ethdev/rte_dev_info.h
> b/lib/librte_ethdev/rte_dev_info.h
> index fea5da8..7a6b61f 100644
> --- a/lib/librte_ethdev/rte_dev_info.h
> +++ b/lib/librte_ethdev/rte_dev_info.h
> @@ -43,7 +43,9 @@ struct rte_eth_dev_module_info {
>  #define RTE_ETH_MODULE_SFF_8472_LEN         512
>  #define RTE_ETH_MODULE_SFF_8636             0x3
>  #define RTE_ETH_MODULE_SFF_8636_LEN         256
> +#define RTE_ETH_MODULE_SFF_8636_MAX_LEN     640
>  #define RTE_ETH_MODULE_SFF_8436             0x4
>  #define RTE_ETH_MODULE_SFF_8436_LEN         256
> +#define RTE_ETH_MODULE_SFF_8436_MAX_LEN     640
> 
>  #endif /* _RTE_DEV_INFO_H_ */
> --
> 1.8.3.1


  reply	other threads:[~2019-09-10  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 11:09 Dekel Peled
2019-09-10  6:11 ` Slava Ovsiienko [this message]
2019-10-09  7:43   ` Ferruh Yigit

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=VI1PR05MB3278C1D5E0263B282247F25AD2B60@VI1PR05MB3278.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=arybchenko@solarflare.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).