>
> On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
> > While writting to device is limitted to max_msg_length advertized in
> > client properites the read can be much longer delivered consequiting
> chunks.
> >
> > We use krealloc to enlarge the buffer when needed.
> >
> >
On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
> While writting to device is limitted to max_msg_length advertized
> in client properites the read can be much longer delivered consequiting
> chunks.
>
> We use krealloc to enlarge the buffer when needed.
>
> Signed-off-by: Tomas
While writting to device is limitted to max_msg_length advertized
in client properites the read can be much longer delivered consequiting chunks.
We use krealloc to enlarge the buffer when needed.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 8
While writting to device is limitted to max_msg_length advertized
in client properites the read can be much longer delivered consequiting chunks.
We use krealloc to enlarge the buffer when needed.
Signed-off-by: Tomas Winkler tomas.wink...@intel.com
---
drivers/misc/mei/bus.c | 8
On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
While writting to device is limitted to max_msg_length advertized
in client properites the read can be much longer delivered consequiting
chunks.
We use krealloc to enlarge the buffer when needed.
Signed-off-by: Tomas Winkler
On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
While writting to device is limitted to max_msg_length advertized in
client properites the read can be much longer delivered consequiting
chunks.
We use krealloc to enlarge the buffer when needed.
Signed-off-by: Tomas
6 matches
Mail list logo