Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933313AbbFWOxI (ORCPT ); Tue, 23 Jun 2015 10:53:08 -0400 Received: from mail-wg0-f41.google.com ([74.125.82.41]:33435 "EHLO mail-wg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932769AbbFWOxD (ORCPT ); Tue, 23 Jun 2015 10:53:03 -0400 From: Antonio Borneo To: Greg Kroah-Hartman , devel@driverdev.osuosl.org Cc: Antonio Borneo , linux-kernel@vger.kernel.org Subject: [PATCH 3/6] staging: mt29f_spinand: Remove redundant spi driver bus initialization Date: Tue, 23 Jun 2015 22:52:39 +0800 Message-Id: <1435071159-24498-1-git-send-email-borneo.antonio@gmail.com> X-Mailer: git-send-email 2.4.4 In-Reply-To: <1435070714-24174-1-git-send-email-borneo.antonio@gmail.com> References: <1435070714-24174-1-git-send-email-borneo.antonio@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1193 Lines: 32 In ancient times it was necessary to manually initialize the bus field of an spi_driver to spi_bus_type. These days this is done in spi_register_driver(), so we can drop the manual assignment. Signed-off-by: Antonio Borneo To: Greg Kroah-Hartman To: devel@driverdev.osuosl.org Cc: linux-kernel@vger.kernel.org --- drivers/staging/mt29f_spinand/mt29f_spinand.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/mt29f_spinand/mt29f_spinand.c b/drivers/staging/mt29f_spinand/mt29f_spinand.c index 7285c64..ad30ce4 100644 --- a/drivers/staging/mt29f_spinand/mt29f_spinand.c +++ b/drivers/staging/mt29f_spinand/mt29f_spinand.c @@ -948,7 +948,6 @@ static const struct of_device_id spinand_dt[] = { static struct spi_driver spinand_driver = { .driver = { .name = "mt29f", - .bus = &spi_bus_type, .owner = THIS_MODULE, .of_match_table = spinand_dt, }, -- 2.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/