linux-kernel - Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <201302072234.44181.arnd@arndb.de>
Date:	Thu, 7 Feb 2013 22:34:44 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Tomas Winkler <tomas.winkler@...el.com>
Cc:	gregkh@...uxfoundation.org, sameo@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next 03/11] mei: bus: Initial implementation for I/O routines

On Thursday 07 February 2013, Tomas Winkler wrote:
> +
> +struct mei_bus_ops {
> +       int (*send)(struct mei_bus_client *client, u8 *buf, size_t length);
> +       int (*recv)(struct mei_bus_client *client, u8 *buf, size_t length);
> +};
> +

Can you have more than one set of mei_bus_ops in a driver? If not,
how about adding the callbacks to the mei_bus_driver structure
directly as a simplification? Never mind if that doesn't work for
some obvious reason I missed.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/