Skip to contentSkip to conversation

spi: Do not require a completion

PATCH New Mark Brown 1 participant 1 message Mar 25, 2014 SPI

lore
Share & tools
lore

Mark Brown

author
#0 lore raw

PATCH 1/1 spi: Do not require a completion

From: Mark Brown <[email protected]>

There is no real reason why we require transfers to have a completion and the only user of the completion now checks to see if one has been provided before using it so stop enforcing this. This makes it more convenient for drivers to chain multiple asynchronous transfers together.

---
 drivers/spi/spi.c | 2 --
 1 file changed, 2 deletions(-)
drivers/spi/spi.c +0 -2
index 26b331d27c35..121c43b5a8e8 100644
@@ -1812,8 +1812,6 @@ static int __spi_validate(struct spi_device *spi, struct spi_message *message)
 
 	if (list_empty(&message->transfers))
 		return -EINVAL;
-	if (!message->complete)
-		return -EINVAL;
 
 	/* Half-duplex links include original MicroWire, and ones with
 	 * only one data pin like SPI_3WIRE (switches direction) or where
Signature · 6 lines
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html