From: Alexander Schmidt <alexs@linux.vnet.ibm.com>
To: Artem <dedekind@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: [PATCH] [MTD] UBI: fix background thread define
Date: Tue, 27 Feb 2007 14:34:28 +0100 [thread overview]
Message-ID: <200702271434.28774.alexs@linux.vnet.ibm.com> (raw)
Hi Artem,
This patch renames DBG_ENABLE_BGT to DBG_DISABLE_BGT, which makes it more
obvious that the background thread should be enabled by default. The name
corresponds to the kernel config option now.
I also fixed the semantics on intialisation (bgt now gets enabled when
DBG_DISABLE_BGT == 0), and compilation with debugging disabled works again.
Signed-off-by: Alexander Schmidt <alexs@linux.vnet.ibm.com>
---
drivers/mtd/ubi/build.c | 2 +-
drivers/mtd/ubi/debug.h | 6 ++++--
2 files changed, 5 insertions(+), 3 deletions(-)
--- dedekind-ubi-2.6.orig/drivers/mtd/ubi/build.c
+++ dedekind-ubi-2.6/drivers/mtd/ubi/build.c
@@ -266,7 +266,7 @@ static int attach_mtd_dev(const char *mt
ubi_msg("number of PEBs reserved for bad PEB handling: %d",
ubi->beb.reserved_pebs);
- if (!DBG_ENABLE_BGT && !ubi->io.ro_mode)
+ if (!DBG_DISABLE_BGT && !ubi->io.ro_mode)
ubi_bgt_enable(ubi);
return 0;
--- dedekind-ubi-2.6.orig/drivers/mtd/ubi/debug.h
+++ dedekind-ubi-2.6/drivers/mtd/ubi/debug.h
@@ -30,9 +30,9 @@
#ifdef CONFIG_MTD_UBI_DEBUG
#ifdef CONFIG_MTD_UBI_DEBUG_DISABLE_BGT
-#define DBG_ENABLE_BGT 0
+#define DBG_DISABLE_BGT 1
#else
-#define DBG_ENABLE_BGT 1
+#define DBG_DISABLE_BGT 0
#endif
#define UBI_DEBUG 1
@@ -142,6 +142,8 @@ void __exit ubi_dbg_close(void);
#define UBI_DEBUG 0
+#define DBG_DISABLE_BGT 0
+
#define ubi_assert(expr) ({})
#define dbg_err(fmt, ...) ({})
next reply other threads:[~2007-02-27 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 13:34 Alexander Schmidt [this message]
2007-02-27 14:09 ` [PATCH] [MTD] UBI: fix background thread define 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=200702271434.28774.alexs@linux.vnet.ibm.com \
--to=alexs@linux.vnet.ibm.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox