From: Joe Perches <joe@perches.com>
To: Robin Murphy <robin.murphy@arm.com>, hch@lst.de
Cc: m.szyprowski@samsung.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, cai@gmx.us, salil.mehta@huawei.com,
john.garry@huawei.com
Subject: Re: [PATCH 1/4] dma-debug: Use pr_fmt()
Date: Tue, 04 Dec 2018 09:35:08 -0800 [thread overview]
Message-ID: <062cb874560a1850d7263a8023ce827f32105fc9.camel@perches.com> (raw)
In-Reply-To: <7d37a451d27828d487d69c7a0662dbe46ece06ec.1543856576.git.robin.murphy@arm.com>
On Mon, 2018-12-03 at 17:28 +0000, Robin Murphy wrote:
> Use pr_fmt() to generate the "DMA-API: " prefix consistently. This
> results in it being added to a couple of pr_*() messages which were
> missing it before, and for the err_printk() calls moves it to the actual
> start of the message instead of somewhere in the middle.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>
> I chose not to refactor the existing split strings for minimal churn here.
>
> kernel/dma/debug.c | 74 ++++++++++++++++++++++++----------------------
> 1 file changed, 38 insertions(+), 36 deletions(-)
>
> diff --git a/kernel/dma/debug.c b/kernel/dma/debug.c
> index 231ca4628062..91b84140e4a5 100644
> --- a/kernel/dma/debug.c
> +++ b/kernel/dma/debug.c
> @@ -17,6 +17,8 @@
> * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
> */
>
> +#define pr_fmt(fmt) "DMA-API: " fmt
> +
> #include <linux/sched/task_stack.h>
> #include <linux/scatterlist.h>
> #include <linux/dma-mapping.h>
> @@ -234,7 +236,7 @@ static bool driver_filter(struct device *dev)
> error_count += 1; \
> if (driver_filter(dev) && \
> (show_all_errors || show_num_errors > 0)) { \
> - WARN(1, "%s %s: " format, \
> + WARN(1, pr_fmt("%s %s: ") format, \
> dev ? dev_driver_string(dev) : "NULL", \
> dev ? dev_name(dev) : "NULL", ## arg); \
> dump_entry_trace(entry); \
I think converting this WARN to
dev_err(dev, format, ##__VA_ARGS__);
dump_stack();
would look better and be more intelligible.
Perhaps add a #define for dev_fmt if really necessary.
next prev parent reply other threads:[~2018-12-04 17:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 17:28 [PATCH 0/4] dma-debug: implement dynamic entry allocation Robin Murphy
2018-12-03 17:28 ` [PATCH 1/4] dma-debug: Use pr_fmt() Robin Murphy
2018-12-04 14:26 ` Christoph Hellwig
2018-12-04 17:35 ` Joe Perches [this message]
2018-12-03 17:28 ` [PATCH 2/4] dma-debug: Refactor dma_debug_entry allocation Robin Murphy
2018-12-04 14:27 ` Christoph Hellwig
2018-12-04 16:09 ` Robin Murphy
2018-12-03 17:28 ` [PATCH 3/4] dma-debug: Dynamically expand the dma_debug_entry pool Robin Murphy
2018-12-03 18:23 ` John Garry
2018-12-04 13:11 ` Robin Murphy
2018-12-04 14:17 ` Christoph Hellwig
2018-12-04 16:06 ` Robin Murphy
2018-12-04 16:30 ` John Garry
2018-12-04 17:19 ` Robin Murphy
2018-12-04 17:38 ` John Garry
2018-12-04 14:29 ` Christoph Hellwig
2018-12-04 16:32 ` Robin Murphy
2018-12-03 17:28 ` [RFC 4/4] dma-debug: Make leak-like behaviour apparent Robin Murphy
2018-12-04 14:31 ` Christoph Hellwig
2018-12-03 17:34 ` [PATCH 0/4] dma-debug: implement dynamic entry allocation Christoph Hellwig
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=062cb874560a1850d7263a8023ce827f32105fc9.camel@perches.com \
--to=joe@perches.com \
--cc=cai@gmx.us \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=salil.mehta@huawei.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®