From mboxrd@z Thu Jan 1 00:00:00 1970 From: sshtylyov@mvista.com (Sergei Shtylyov) Date: Wed, 15 Dec 2010 16:25:28 +0300 Subject: [PATCH] MTD: m25p80: add debugging trace in sst_write() In-Reply-To: <1292414372-17085-1-git-send-email-nicolas.ferre@atmel.com> References: <1292414372-17085-1-git-send-email-nicolas.ferre@atmel.com> Message-ID: <4D08C1C8.3090100@ru.mvista.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello. On 15-12-2010 14:59, Nicolas Ferre wrote: > Add a DEBUG(MTD_DEBUG_LEVEL2, ..) trace at beginning of sst_write() function as > it is done in m25p80_write() function. > Signed-off-by: Nicolas Ferre [...] > diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c > index bf5a002..e6b5707 100644 > --- a/drivers/mtd/devices/m25p80.c > +++ b/drivers/mtd/devices/m25p80.c > @@ -482,6 +482,10 @@ static int sst_write(struct mtd_info *mtd, loff_t to, size_t len, > size_t actual; > int cmd_sz, ret; > > + DEBUG(MTD_DEBUG_LEVEL2, "%s: %s %s 0x%08x, len %zd\n", > + dev_name(&flash->spi->dev), __func__, "to", What's the point of printing "to" as variable? :-) > + (u32)to, len); > + WBR, Sergei