From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 2/2] drivers: replace printf with fprintf for debug functions
Date: Thu, 16 Feb 2023 14:57:23 +0530 [thread overview]
Message-ID: <2f98a10d-0be8-5164-b213-97553ea76209@oss.nxp.com> (raw)
In-Reply-To: <10101166.0AQdONaE2F@thomas>
On 15-Feb-23 8:46 PM, Thomas Monjalon wrote:
> 15/02/2023 11:29, Hemant Agrawal:
>> This patch replaces simple printf with fprintf for debug dump
>> related functions for various NXP dpaaX related drivers.
> Why replacing with fprintf(stdout)?
>
> Would it be better to provide a FILE* parameter to the functions?
yes, I will update.
>
>
>
next prev parent reply other threads:[~2023-02-16 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 10:29 [PATCH 1/2] drivers: replace printf with log macros Hemant Agrawal
2023-02-15 10:29 ` [PATCH 2/2] drivers: replace printf with fprintf for debug functions Hemant Agrawal
2023-02-15 15:16 ` Thomas Monjalon
2023-02-16 9:27 ` Hemant Agrawal [this message]
2023-02-15 17:17 ` Stephen Hemminger
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=2f98a10d-0be8-5164-b213-97553ea76209@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=thomas@monjalon.net \
/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).