public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Salah Triki <salah.triki@gmail.com>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	viro@zeniv.linux.org.uk, mhocko@suse.com, vdavydov@virtuozzo.com,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] fs: befs: check silent flag before logging error
Date: Thu, 28 Jul 2016 01:09:03 +0100	[thread overview]
Message-ID: <20160728000903.GC3942@pc> (raw)
In-Reply-To: <1467232061-5600-1-git-send-email-luisbg@osg.samsung.com>

On Wed, Jun 29, 2016 at 09:27:40PM +0100, Luis de Bethencourt wrote:
> Log error only when silent flag is not set.
> 
> Fixes: dbe6460388bc ("fs/befs/linuxvfs.c: check silent flag before logging errors")
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
> 
> Hi,
> 
> Reading the backlog of latest patches to befs, I noticed that Salah's patch
> missed one call to befs_error() when setting all to only be used when the
> silent argument is false.
> 
> Thanks,
> Luis
> 
>  fs/befs/linuxvfs.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/befs/linuxvfs.c b/fs/befs/linuxvfs.c
> index b700645..bf5658d 100644
> --- a/fs/befs/linuxvfs.c
> +++ b/fs/befs/linuxvfs.c
> @@ -790,7 +790,8 @@ befs_fill_super(struct super_block *sb, void *data, int silent)
>  	 */ 
>  	blocksize = sb_min_blocksize(sb, 1024);
>  	if (!blocksize) {
> -		befs_error(sb, "unable to set blocksize");
> +		if (!silent)
> +			befs_error(sb, "unable to set blocksize");
>  		goto unacquire_priv_sbp;
>  	}
>  
> -- 
> 2.5.1
> 

Acked-by: Salah Triki <salah.triki@gmail.com>

regards,
salah

      parent reply	other threads:[~2016-07-28  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 20:27 [PATCH 1/2] fs: befs: check silent flag before logging error Luis de Bethencourt
2016-06-29 20:27 ` [PATCH 2/2] fs: befs: remove comment that confuses kernel-doc Luis de Bethencourt
2016-07-28  0:09 ` Salah Triki [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=20160728000903.GC3942@pc \
    --to=salah.triki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=mhocko@suse.com \
    --cc=vdavydov@virtuozzo.com \
    --cc=viro@zeniv.linux.org.uk \
    /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