All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Ocfs2-tools-devel] [PATCH 2/2] features: Make inline-data a default feature
Date: Tue, 06 Jan 2009 15:53:48 -0800	[thread overview]
Message-ID: <4963EF0C.7000700@oracle.com> (raw)
In-Reply-To: <1230330267-1975-2-git-send-email-mfasheh@suse.com>

sob

man page will need tweaking. ;) I can handle that later.

Mark Fasheh wrote:
> Kernels since 2.6.24 have supported this, I think it's time to make it a
> default feature.
>
> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
> ---
>  libocfs2/feature_string.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/libocfs2/feature_string.c b/libocfs2/feature_string.c
> index 7b1f93e..e6633da 100644
> --- a/libocfs2/feature_string.c
> +++ b/libocfs2/feature_string.c
> @@ -62,7 +62,8 @@ static struct feature_level_translation ocfs2_feature_levels_table[] = {
>  
>  static ocfs2_fs_options feature_level_defaults[] = {
>  	{OCFS2_FEATURE_COMPAT_BACKUP_SB | OCFS2_FEATURE_COMPAT_JBD2_SB,
> -	 OCFS2_FEATURE_INCOMPAT_SPARSE_ALLOC,
> +	 OCFS2_FEATURE_INCOMPAT_SPARSE_ALLOC |
> +	 OCFS2_FEATURE_INCOMPAT_INLINE_DATA,
>  	 OCFS2_FEATURE_RO_COMPAT_UNWRITTEN},  /* OCFS2_FEATURE_LEVEL_DEFAULT */
>  
>  	{OCFS2_FEATURE_COMPAT_BACKUP_SB | OCFS2_FEATURE_COMPAT_JBD2_SB,
>   

  parent reply	other threads:[~2009-01-06 23:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 22:24 [Ocfs2-devel] [PATCH 1/2] mkfs.ocfs2: Update fs-features list in man page Mark Fasheh
2008-12-26 22:24 ` [Ocfs2-devel] [PATCH 2/2] features: Make inline-data a default feature Mark Fasheh
2008-12-26 22:28   ` Mark Fasheh
2008-12-29  0:33     ` Tao Ma
2009-01-06 23:54       ` Sunil Mushran
2009-01-06 23:53   ` Sunil Mushran [this message]
2008-12-29  0:34 ` [Ocfs2-devel] [PATCH 1/2] mkfs.ocfs2: Update fs-features list in man page Tao Ma
2009-01-06 23:49 ` [Ocfs2-devel] [Ocfs2-tools-devel] " Sunil Mushran
2009-01-08  0:55   ` Mark Fasheh
2009-01-08  1:09     ` Sunil Mushran

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=4963EF0C.7000700@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.