diff options
| author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2008-10-21 12:56:31 +0300 |
|---|---|---|
| committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2008-11-06 11:06:14 +0200 |
| commit | 069782a1ee55105220e5ae2db448495dac267cb1 (patch) | |
| tree | b25f2fadb18c795e04761d1a5c8bbdcba5589bcd | |
| parent | 45beca08dd8b6d6a65c5ffd730af2eac7a2c7a03 (diff) | |
| download | linux-3.10-069782a1ee55105220e5ae2db448495dac267cb1.tar.gz linux-3.10-069782a1ee55105220e5ae2db448495dac267cb1.tar.bz2 linux-3.10-069782a1ee55105220e5ae2db448495dac267cb1.zip | |
UBIFS: remove printk
Remove the "UBIFS background thread ubifs_bgd0_0 started" message.
We kill the background thread when we switch to R/O mode, and
start it again whan we switch to R/W mode. OLPC is doing this
many times during boot, and we see this message many times as
well, which is irritating. So just kill the message.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
| -rw-r--r-- | fs/ubifs/commit.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/ubifs/commit.c b/fs/ubifs/commit.c index 0a6aa2cc78f..b49884c8c10 100644 --- a/fs/ubifs/commit.c +++ b/fs/ubifs/commit.c @@ -234,8 +234,8 @@ int ubifs_bg_thread(void *info) int err; struct ubifs_info *c = info; - ubifs_msg("background thread \"%s\" started, PID %d", - c->bgt_name, current->pid); + dbg_msg("background thread \"%s\" started, PID %d", + c->bgt_name, current->pid); set_freezable(); while (1) { |