public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: yargil@free.fr
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4: don't work without procfs
Date: Thu, 06 Oct 2011 14:48:54 +0200	[thread overview]
Message-ID: <1317905334.4e8da3b62b99c@imp.free.fr> (raw)
In-Reply-To: <alpine.LFD.2.00.1110051456440.4423@dhcp-27-109.brq.redhat.com>

Selon Lukas Czerner <lczerner@redhat.com>:

Thanks for your review. But shame on me, i just found out that I did not follow
the procedure to submit the patch and it is not Signed-off-by. I will resubmit
you this patch by following the linux/Documentation/SubmittingPatches.

> On Tue, 4 Oct 2011, Yargil wrote:
>
> > Regression from commit dd68314ccf3fb918c1fb6471817edbc60ece4b52
> > The problem come from the test of the return value of proc_mkdir
> > that is always false without procfs and abort the init of ext4.
>
> Looks good. Thanks!
>
> Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> > ---
> >  fs/ext4/super.c |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> > index 44d0c8d..9b51b17 100644
> > --- a/fs/ext4/super.c
> > +++ b/fs/ext4/super.c
> > @@ -4985,8 +4985,10 @@ static int __init ext4_init_fs(void)
> >  	if (!ext4_kset)
> >  		goto out6;
> >  	ext4_proc_root = proc_mkdir("fs/ext4", NULL);
> > +#ifdef CONFIG_PROC_FS
> >  	if (!ext4_proc_root)
> >  		goto out5;
> > +#endif
> >
> >  	err = ext4_init_feat_adverts();
> >  	if (err)
> >
>
> --
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



      reply	other threads:[~2011-10-06 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 15:44 [PATCH v2] ext4: don't work without procfs Yargil
2011-10-05 13:00 ` Lukas Czerner
2011-10-06 12:48   ` yargil [this message]

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=1317905334.4e8da3b62b99c@imp.free.fr \
    --to=yargil@free.fr \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox