From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MTD: m25p80: add debugging trace in sst_write()
Date: Sun, 19 Dec 2010 19:00:55 +0200 [thread overview]
Message-ID: <1292778055.13362.8.camel@koala> (raw)
In-Reply-To: <1292414372-17085-1-git-send-email-nicolas.ferre@atmel.com>
On Wed, 2010-12-15 at 12:59 +0100, 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 <nicolas.ferre@atmel.com>
So do you do this only becaus it is done in m25p80_write()? This is what
the commit message suggests... Have you found these DEBUG macros useful
for you? (I never found them any useful).
Anyway, I've put this to my l2-mtd-2.6.git tree, thanks.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MTD: m25p80: add debugging trace in sst_write()
Date: Sun, 19 Dec 2010 19:00:55 +0200 [thread overview]
Message-ID: <1292778055.13362.8.camel@koala> (raw)
In-Reply-To: <1292414372-17085-1-git-send-email-nicolas.ferre@atmel.com>
On Wed, 2010-12-15 at 12:59 +0100, 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 <nicolas.ferre@atmel.com>
So do you do this only becaus it is done in m25p80_write()? This is what
the commit message suggests... Have you found these DEBUG macros useful
for you? (I never found them any useful).
Anyway, I've put this to my l2-mtd-2.6.git tree, thanks.
--
Best Regards,
Artem Bityutskiy (???????? ?????)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MTD: m25p80: add debugging trace in sst_write()
Date: Sun, 19 Dec 2010 19:00:55 +0200 [thread overview]
Message-ID: <1292778055.13362.8.camel@koala> (raw)
In-Reply-To: <1292414372-17085-1-git-send-email-nicolas.ferre@atmel.com>
On Wed, 2010-12-15 at 12:59 +0100, 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 <nicolas.ferre@atmel.com>
So do you do this only becaus it is done in m25p80_write()? This is what
the commit message suggests... Have you found these DEBUG macros useful
for you? (I never found them any useful).
Anyway, I've put this to my l2-mtd-2.6.git tree, thanks.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-12-19 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 11:59 [PATCH] MTD: m25p80: add debugging trace in sst_write() Nicolas Ferre
2010-12-15 11:59 ` Nicolas Ferre
2010-12-15 11:59 ` Nicolas Ferre
2010-12-15 13:25 ` Sergei Shtylyov
2010-12-15 13:25 ` Sergei Shtylyov
2010-12-15 13:25 ` Sergei Shtylyov
2010-12-15 13:43 ` Nicolas Ferre
2011-07-08 16:43 ` Nicolas Ferre
2010-12-15 13:43 ` Nicolas Ferre
2010-12-15 16:12 ` Russell King - ARM Linux
2010-12-15 16:12 ` Russell King - ARM Linux
2010-12-15 16:12 ` Russell King - ARM Linux
2010-12-19 17:00 ` Artem Bityutskiy [this message]
2010-12-19 17:00 ` Artem Bityutskiy
2010-12-19 17:00 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292778055.13362.8.camel@koala \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@atmel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.