linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: John Pittman <jpittman@redhat.com>
Cc: esandeen@redhat.com, preichl@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3] xfsprogs: add missing line feeds in libxfs/rdwr.c
Date: Tue, 26 Nov 2019 10:33:44 +0100	[thread overview]
Message-ID: <20191126093344.l43sriu2jm7gvqsq@orion> (raw)
In-Reply-To: <20191123155508.15769-1-jpittman@redhat.com>

On Sat, Nov 23, 2019 at 10:55:08AM -0500, John Pittman wrote:
> In libxfs/rdwr.c, there are several fprintf() calls that are
> missing trailing line feeds. This translates to the following
> CLI prompt being on the same line as the message. Add missing
> line feeds, alleviating the issue.
> 
> Fixes: 0a7942b38215 ("libxfs: don't discard dirty buffers")
> Signed-off-by: John Pittman <jpittman@redhat.com>

Despite my Reviewed-by previously, next patches, please don't forget to also
provide the changelog for your Vx patches.

> ---

^ Changelogs should go below this line, so they are not propagated to the git
tree, but it's really helpful to understand why you needed to send new versions.

Cheers.

>  libxfs/rdwr.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/libxfs/rdwr.c b/libxfs/rdwr.c
> index 7080cd9c..3f69192d 100644
> --- a/libxfs/rdwr.c
> +++ b/libxfs/rdwr.c
> @@ -651,7 +651,7 @@ __libxfs_getbufr(int blen)
>  	pthread_mutex_unlock(&xfs_buf_freelist.cm_mutex);
>  	bp->b_ops = NULL;
>  	if (bp->b_flags & LIBXFS_B_DIRTY)
> -		fprintf(stderr, "found dirty buffer (bulk) on free list!");
> +		fprintf(stderr, "found dirty buffer (bulk) on free list!\n");
>  
>  	return bp;
>  }
> @@ -1224,7 +1224,7 @@ libxfs_brelse(
>  		return;
>  	if (bp->b_flags & LIBXFS_B_DIRTY)
>  		fprintf(stderr,
> -			"releasing dirty buffer to free list!");
> +			"releasing dirty buffer to free list!\n");
>  
>  	pthread_mutex_lock(&xfs_buf_freelist.cm_mutex);
>  	list_add(&bp->b_node.cn_mru, &xfs_buf_freelist.cm_list);
> @@ -1245,7 +1245,7 @@ libxfs_bulkrelse(
>  	list_for_each_entry(bp, list, b_node.cn_mru) {
>  		if (bp->b_flags & LIBXFS_B_DIRTY)
>  			fprintf(stderr,
> -				"releasing dirty buffer (bulk) to free list!");
> +				"releasing dirty buffer (bulk) to free list!\n");
>  		count++;
>  	}
>  
> -- 
> 2.17.2
> 

-- 
Carlos


      parent reply	other threads:[~2019-11-26  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 15:55 [PATCH v3] xfsprogs: add missing line feeds in libxfs/rdwr.c John Pittman
2019-11-25 18:08 ` Pavel Reichl
2019-11-26  9:31 ` Carlos Maiolino
2019-11-26  9:33 ` Carlos Maiolino [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=20191126093344.l43sriu2jm7gvqsq@orion \
    --to=cmaiolino@redhat.com \
    --cc=esandeen@redhat.com \
    --cc=jpittman@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=preichl@redhat.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;
as well as URLs for NNTP newsgroup(s).