From: John Pittman <jpittman@redhat.com>
To: Pavel Reichl <preichl@redhat.com>
Cc: Eric Sandeen <esandeen@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfsprogs: add missing carriage returns in libxfs/rdwr.c
Date: Sat, 23 Nov 2019 10:44:29 -0500 [thread overview]
Message-ID: <CA+RJvhy6Dmr=fgCDhub3hcOr1m3gvanXshXCE4HPQzjS7eLF=Q@mail.gmail.com> (raw)
In-Reply-To: <CAJc7PzWPv5UHMWb+twW6g8tWLCFX_6aRTaH6F3bXLsRmZxaZvQ@mail.gmail.com>
You're exactly right Pavel; thanks for the clarification. Sending v2 now.
On Sat, Nov 23, 2019 at 2:08 AM Pavel Reichl <preichl@redhat.com> wrote:
>
> On Fri, Nov 22, 2019 at 10:31 PM John Pittman <jpittman@redhat.com> wrote:
> >
> > In libxfs/rdwr.c, there are several fprintf() calls that are
> > missing trailing carriage returns. This translates to the
> > following CLI prompt being on the same line as the message.
> > Add missing carriage returns, alleviating the issue.
> >
> > Fixes: 0a7942b38215 ("libxfs: don't discard dirty buffers")
> > Signed-off-by: John Pittman <jpittman@redhat.com>
> > ---
> > 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
> >
>
> Hello John,
>
> it seems to me that you are confusing carriage return (CR, \r) and
> line feed (LF, \n) in the commit description. Could you check that
> out, please? Otherwise it looks good to me.
>
> Thanks.
>
> Pave Reichl
>
prev parent reply other threads:[~2019-11-23 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 21:31 [PATCH] xfsprogs: add missing carriage returns in libxfs/rdwr.c John Pittman
2019-11-23 7:07 ` Pavel Reichl
2019-11-23 15:44 ` John Pittman [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='CA+RJvhy6Dmr=fgCDhub3hcOr1m3gvanXshXCE4HPQzjS7eLF=Q@mail.gmail.com' \
--to=jpittman@redhat.com \
--cc=esandeen@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).