[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201302111152.42483.arnd@arndb.de>
Date: Mon, 11 Feb 2013 11:52:42 +0000
From: Arnd Bergmann <arnd@...db.de>
To: Samuel Ortiz <sameo@...ux.intel.com>
Cc: Tomas Winkler <tomas.winkler@...el.com>,
gregkh@...uxfoundation.org, 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, Samuel Ortiz wrote:
> On Thu, Feb 07, 2013 at 10:34:44PM +0000, Arnd Bergmann wrote:
> > 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?
> You can have at most one mei_bus_ops per mei_bus_client.
>
> > If not, how about adding the callbacks to the mei_bus_driver structure
> > directly as a simplification?
> I can add the ops directly to the mei_bus_client structure, yes.
I looked at the new version, and it's not what I assumed it would be.
I thought the operations were specific to a client driver and should
be part of the /mei_bus_driver/ structure, not the /mei_bus_client/.
Did I misunderstand what these functions do, or did you misunderstand
what I was asking for?
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/
Powered by blists - more mailing lists