From patchwork Sun Feb 12 09:13:08 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: sfc: mtd: Use MTD_FAIL_ADDR_UNKNOWN instead of 0xffffffff Date: Sat, 11 Feb 2012 23:13:08 -0000 From: Shmulik Ladkani X-Patchwork-Id: 140807 Message-Id: <20120212111308.0267f200@pixies.home.jungo.com> To: Ben Hutchings , linux-net-drivers@solarflare.com, linux-mtd@lists.infradead.org Cc: netdev@vger.kernel.org, shmulik.ladkani@gmail.com, Artem Bityutskiy From: Shmulik Ladkani As of bb0eb217, MTD_FAIL_ADDR_UNKNOWN should be used to indicate mtd erase failure not specific to any particular block. Use MTD_FAIL_ADDR_UNKNOWN instead of 0xffffffff when setting 'erase->fail_addr' in 'efx_mtd_erase()'. Signed-off-by: Shmulik Ladkani Acked-by: Ben Hutchings --- diff --git a/drivers/net/ethernet/sfc/mtd.c b/drivers/net/ethernet/sfc/mtd.c index 6622eca..c44a03e 100644 --- a/drivers/net/ethernet/sfc/mtd.c +++ b/drivers/net/ethernet/sfc/mtd.c @@ -193,7 +193,7 @@ static int efx_mtd_erase(struct mtd_info *mtd, struct erase_info *erase) erase->state = MTD_ERASE_DONE; } else { erase->state = MTD_ERASE_FAILED; - erase->fail_addr = 0xffffffff; + erase->fail_addr = MTD_FAIL_ADDR_UNKNOWN; } mtd_erase_callback(erase); return rc;