linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gow <davidgow@google.com>
To: Marco Elver <elver@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	Alan Maguire <alan.maguire@oracle.com>,
	frank.rowand@sony.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] kunit: Add missing newline in summary message
Date: Fri, 17 Apr 2020 10:55:34 +0800	[thread overview]
Message-ID: <CABVgOSniuRdx1KjMLTZCJ3gWJo7rsrotpy0yfDhRCLqbjmgp-w@mail.gmail.com> (raw)
In-Reply-To: <20200416114256.226329-1-elver@google.com>

On Thu, Apr 16, 2020 at 7:43 PM 'Marco Elver' via KUnit Development
<kunit-dev@googlegroups.com> wrote:
>
> Add missing newline, as otherwise flushing of the final summary message
> to the console log can be delayed.
>
> Fixes: e2219db280e3 ("kunit: add debugfs /sys/kernel/debug/kunit/<suite>/results display")
> Signed-off-by: Marco Elver <elver@google.com>

Tested-by: David Gow <davidgow@google.com>

Thanks a lot: this issue was starting to get annoying, and I can
confirm this patch fixes it for me!

-- David

  reply	other threads:[~2020-04-17  2:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 11:42 [PATCH] kunit: Add missing newline in summary message Marco Elver
2020-04-17  2:55 ` David Gow [this message]
2020-04-17 10:03 ` Alan Maguire
2020-04-22 11:05   ` Marco Elver
2020-04-22 19:37     ` Brendan Higgins
2020-04-22 19:35 ` Brendan Higgins
2020-04-23 22:07   ` Shuah Khan

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=CABVgOSniuRdx1KjMLTZCJ3gWJo7rsrotpy0yfDhRCLqbjmgp-w@mail.gmail.com \
    --to=davidgow@google.com \
    --cc=alan.maguire@oracle.com \
    --cc=brendanhiggins@google.com \
    --cc=elver@google.com \
    --cc=frank.rowand@sony.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).