- spi-documentation-does-not-need-to-set-drivers-bus_type-field.patch removed from -mm tree

- spi-documentation-does-not-need-to-set-drivers-bus_type-field.patch removed from -mm tree

[akpm]

The patch titled
     spi: documentation does not need to set driver's bus_type field
has been removed from the -mm tree.  Its filename was
     spi-documentation-does-not-need-to-set-drivers-bus_type-field.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
Subject: spi: documentation does not need to set driver's bus_type field
From: Ben Dooks <ben@fluff.org>

The spi_register_driver() sets the bus_type field of the spi_driver being
registered, so there is no need to have it set in the driver itself.

Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/spi/spi-summary |    1 -
 1 file changed, 1 deletion(-)

diff -puN Documentation/spi/spi-summary~spi-documentation-does-not-need-to-set-drivers-bus_type-field Documentation/spi/spi-summary
--- a/Documentation/spi/spi-summary~spi-documentation-does-not-need-to-set-drivers-bus_type-field
+++ a/Documentation/spi/spi-summary
@@ -284,7 +284,6 @@ SPI protocol drivers somewhat resemble p
 	static struct spi_driver CHIP_driver = {
 		.driver = {
 			.name		= "CHIP",
-			.bus		= &spi_bus_type,
 			.owner		= THIS_MODULE,
 		},
 
_

Patches currently in -mm which might be from ben@fluff.org are

origin.patch