netdev - Re: [Crypto v4 01/12] tls: tls_device struct to register TLS drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180212.144516.999297130875943550.davem@davemloft.net>
Date:   Mon, 12 Feb 2018 14:45:16 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     atul.gupta@...lsio.com
Cc:     davejwatson@...com, herbert@...dor.apana.org.au,
        sd@...asysnail.net, linux-crypto@...r.kernel.org,
        netdev@...r.kernel.org, ganeshgr@...lsio.com
Subject: Re: [Crypto v4 01/12] tls: tls_device struct to register TLS
 drivers

From: Atul Gupta <atul.gupta@...lsio.com>
Date: Mon, 12 Feb 2018 17:33:48 +0530

> +	/* When calling get_netdev, the HW vendor's driver should return the
> +	 * net device of device @device at port @port_num or NULL if such
> +	 * a net device doesn't exist
> +	 */
> +	struct net_device *(*netdev)(struct tls_device *device,
> +				     struct net_device *netdev);

I do not see a "port_num" parameter or structure member anywhere.

Please update this comment to match reality.

Thank you.