Hi Geert,
On Mon, Feb 17, 2014 at 07:02:09PM +0100, Geert Uytterhoeven wrote:
> On Mon, Feb 17, 2014 at 6:20 PM, Maxime Ripard
> wrote:
> > When the generic implementation of the transfer_one_message callback was
> > called
> > by the spi_pump_messages function, if that transfer was to fail,
On Mon, Feb 17, 2014 at 6:20 PM, Maxime Ripard
wrote:
> When the generic implementation of the transfer_one_message callback was
> called
> by the spi_pump_messages function, if that transfer was to fail, the
> spi_finalize_current_message was called twice, once in
> spi_transfer_one_message,
When the generic implementation of the transfer_one_message callback was called
by the spi_pump_messages function, if that transfer was to fail, the
spi_finalize_current_message was called twice, once in
spi_transfer_one_message, and one in spi_pump_messages.
This was causing a null pointer
When the generic implementation of the transfer_one_message callback was called
by the spi_pump_messages function, if that transfer was to fail, the
spi_finalize_current_message was called twice, once in
spi_transfer_one_message, and one in spi_pump_messages.
This was causing a null pointer
On Mon, Feb 17, 2014 at 6:20 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
When the generic implementation of the transfer_one_message callback was
called
by the spi_pump_messages function, if that transfer was to fail, the
spi_finalize_current_message was called twice, once in
Hi Geert,
On Mon, Feb 17, 2014 at 07:02:09PM +0100, Geert Uytterhoeven wrote:
On Mon, Feb 17, 2014 at 6:20 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
When the generic implementation of the transfer_one_message callback was
called
by the spi_pump_messages function, if that
6 matches
Mail list logo