From: Leon Romanovsky <leonro@mellanox.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Joe Perches <joe@perches.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
matanb@mellanox.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/mlx5:: pr_err() and mlx5_ib_dbg() strings should end with newlines
Date: Wed, 27 Sep 2017 17:46:44 +0300 [thread overview]
Message-ID: <20170927144644.GE2297@mtr-leonro.local> (raw)
In-Reply-To: <1506522039.82712.26.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Wed, Sep 27, 2017 at 10:20:39AM -0400, Doug Ledford wrote:
> On Tue, 2017-09-26 at 12:11 -0700, Joe Perches wrote:
> > On Tue, 2017-09-26 at 18:50 +0300, Leon Romanovsky wrote:
> > > So how can I reproduce the different output before and after this
> > > change?
> >
> > Try lib/test_module.c with and without the newline
> > on "Hello, World" on a quiescent system.
>
> I agree here. The newlines are still worthwhile as they remove any
> unnecessary stalls in the printk output while the printk engine decides
> whether or not you are going to do a KERN_CONT print next.
>
> Thanks, applied.
Thanks
>
> --
> Doug Ledford <dledford@redhat.com>
> GPG KeyID: B826A3330E572FDD
> Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-09-27 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 6:50 [PATCH] IB/mlx5:: pr_err() and mlx5_ib_dbg() strings should end with newlines Arvind Yadav
[not found] ` <7a5a195cd37db476a2ca007eddc0f28f3ade265b.1506407876.git.arvind.yadav.cs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-26 7:07 ` Yuval Shaia
2017-09-26 8:38 ` Leon Romanovsky
[not found] ` <20170926083843.GB6816-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 15:05 ` Joe Perches
2017-09-26 15:50 ` Leon Romanovsky
2017-09-26 19:11 ` Joe Perches
[not found] ` <1506453105.29089.14.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-09-27 14:20 ` Doug Ledford
2017-09-27 14:46 ` Leon Romanovsky [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=20170927144644.GE2297@mtr-leonro.local \
--to=leonro@mellanox.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=sean.hefty@intel.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