mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Dave Kleikamp <shaggy@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
	Amir Goldstein <amir73il@gmail.com>,
	Chengming Zhou <zhouchengming@bytedance.com>,
	jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] jfs: Delete a couple tabs in jfs_reconfigure()
Date: Wed, 2 Oct 2024 08:31:06 -0500	[thread overview]
Message-ID: <09db55b6-385b-46e1-92e7-ee4dbfe439de@redhat.com> (raw)
In-Reply-To: <12768f55-47e6-4bfa-aa63-0a82b911e098@stanley.mountain>

On 10/2/24 3:37 AM, Dan Carpenter wrote:
> This is just a small white space cleanup.  The conversion to the new
> mount api accidentally added an extra indent on these lines.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>

Ugh, oops, thanks.

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

> ---
>  fs/jfs/super.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/jfs/super.c b/fs/jfs/super.c
> index 223d9ac59839..508666d4ed01 100644
> --- a/fs/jfs/super.c
> +++ b/fs/jfs/super.c
> @@ -389,8 +389,8 @@ static int jfs_reconfigure(struct fs_context *fc)
>  
>  		if (!ctx->newLVSize) {
>  			ctx->newLVSize = sb_bdev_nr_blocks(sb);
> -				if (ctx->newLVSize == 0)
> -					pr_err("JFS: Cannot determine volume size\n");
> +			if (ctx->newLVSize == 0)
> +				pr_err("JFS: Cannot determine volume size\n");
>  		}
>  
>  		rc = jfs_extendfs(sb, ctx->newLVSize, 0);


      reply	other threads:[~2024-10-02 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  8:37 Dan Carpenter
2024-10-02 13:31 ` Eric Sandeen [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=09db55b6-385b-46e1-92e7-ee4dbfe439de@redhat.com \
    --to=sandeen@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=jlayton@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@kernel.org \
    --cc=zhouchengming@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®