Re: [RFC PATCH 26/26] UBIFS: include FS to compilation

From: Pekka Enberg
Date: Tue Apr 01 2008 - 03:39:29 EST


Hi Artem,

On Thu, Mar 27, 2008 at 5:55 PM, Artem Bityutskiy
<Artem.Bityutskiy@xxxxxxxxx> wrote:
> +config UBIFS_FS_DEBUG_MSG_GEN
> +
> +config UBIFS_FS_DEBUG_MSG_JRN
> +
> +config UBIFS_FS_DEBUG_MSG_CMT
> +
> +config UBIFS_FS_DEBUG_MSG_BUDG
> +
> +config UBIFS_FS_DEBUG_MSG_LOG
> +
> +config UBIFS_FS_DEBUG_MSG_TNC
> +
> +config UBIFS_FS_DEBUG_MSG_LP
> +
> +config UBIFS_FS_DEBUG_MSG_FIND
> +
> +config UBIFS_FS_DEBUG_MSG_MNT
> +
> +config UBIFS_FS_DEBUG_MSG_IO
> +
> +config UBIFS_FS_DEBUG_MSG_GC
> +
> +config UBIFS_FS_DEBUG_MSG_SCAN

But these don't make much sense to me. Why would you want to be able
to compile out printks at this granularity? Why not enable all of them
when CONFIG_UBIFS_FS_DEBUG is enabled?

> +menu "Extra self-checks"
> + depends on UBIFS_FS_DEBUG
> +
> +config UBIFS_FS_DEBUG_CHK_MEMPRESS

> +config UBIFS_FS_DEBUG_CHK_LPROPS
> +
> +config UBIFS_FS_DEBUG_CHK_TNC
> +
> +config UBIFS_FS_DEBUG_CHK_ORPH
> +
> +config UBIFS_FS_DEBUG_CHK_IDX_SZ
> +
> +config UBIFS_FS_DEBUG_CHK_OLD_IDX
> +
> +config UBIFS_FS_DEBUG_CHK_OTHER
> +
> +config UBIFS_FS_DEBUG_TEST_RCVRY

Why would you not want to enable all of these for development kernels?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/