The patch titled
Subject: jbd: drop jbd_ENOSYS debug
has been removed from the -mm tree. Its filename was
jbd-drop-jbd_enosys-debug.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Davidlohr Bueso <dave@xxxxxxxxxxxx>
Subject: jbd: drop jbd_ENOSYS debug
A quick search shows that there are no users, drop the macro for both jbd
and jbd2.
Signed-off-by: Davidlohr Bueso <dbueso@xxxxxxx>
Cc: Jan Kara <jack@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/jbd.h | 9 ---------
include/linux/jbd2.h | 9 ---------
2 files changed, 18 deletions(-)
diff -puN include/linux/jbd.h~jbd-drop-jbd_enosys-debug include/linux/jbd.h
--- a/include/linux/jbd.h~jbd-drop-jbd_enosys-debug
+++ a/include/linux/jbd.h
@@ -956,15 +956,6 @@ void __log_wait_for_space(journal_t *jou
extern void __journal_drop_transaction(journal_t *, transaction_t *);
extern int cleanup_journal_tail(journal_t *);
-/* Debugging code only: */
-
-#define jbd_ENOSYS() \
-do { \
- printk (KERN_ERR "JBD unimplemented function %s\n", __func__); \
- current->state = TASK_UNINTERRUPTIBLE; \
- schedule(); \
-} while (1)
-
/*
* is_journal_abort
*
diff -puN include/linux/jbd2.h~jbd-drop-jbd_enosys-debug include/linux/jbd2.h
--- a/include/linux/jbd2.h~jbd-drop-jbd_enosys-debug
+++ a/include/linux/jbd2.h
@@ -1251,15 +1251,6 @@ void __jbd2_log_wait_for_space(journal_t
extern void __jbd2_journal_drop_transaction(journal_t *, transaction_t *);
extern int jbd2_cleanup_journal_tail(journal_t *);
-/* Debugging code only: */
-
-#define jbd_ENOSYS() \
-do { \
- printk (KERN_ERR "JBD unimplemented function %s\n", __func__); \
- current->state = TASK_UNINTERRUPTIBLE; \
- schedule(); \
-} while (1)
-
/*
* is_journal_abort
*
_
Patches currently in -mm which might be from dave@xxxxxxxxxxxx are
signal-use-current-state-helpers.patch
ipcsem-use-current-state-helpers.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
