zlogger: remove outdated comment

The comment isn't outright false, as the userspace might really be using
the block. However, 3a489d20b218eec5073f18e5b248ced6c6a843d8 handles
exactly that case, so it is completely normal and correct to unmap the
block that is in use.

Change-Id: Icc4bec0268a3cba23990e35fb36448851ca4fb1f
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>

diff --git a/kernel/zlogger/zlogger.c b/kernel/zlogger/zlogger.c
index 427ebf61fcd24f7d5f381c56e58db5f6c8c3e203..1c047a961cec2be645b0a0d0d9a96e29e9be8c12 100644 (file)
--- a/kernel/zlogger/zlogger.c
+++ b/kernel/zlogger/zlogger.c
@@ -262,7 +262,6 @@ static int zlog_task(void *user_data)
                        if (blk && get_block(blk)->head.ts < g_start_time) {
                                get_block(blk)->head.tid = 0;
                                ptr->blk = 0;
-                               // TODO: The userspace might very well be using this block right now.
                                zlogger_unmap(ptr);
                                mutex_lock(&g_block_mutex);
                                queue_push(&g_free_q, blk);