From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: ferruh.yigit@amd.com, Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH] devtools: forbid writing to standard output streams
Date: Fri, 19 Jan 2024 12:09:15 +0100 [thread overview]
Message-ID: <CAJFAV8x6QFg-+CPMPYPzAiTz_3NFnGg9cz2fa0hfZ9oJJ3eJsw@mail.gmail.com> (raw)
In-Reply-To: <20231221133120.1654941-1-david.marchand@redhat.com>
On Thu, Dec 21, 2023 at 2:31 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> No output on stdout or stderr!
> Drivers and libraries must use the logging framework.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-01-19 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:31 David Marchand
2023-12-21 14:52 ` Bruce Richardson
2023-12-21 16:30 ` Stephen Hemminger
2023-12-21 17:06 ` Tyler Retzlaff
2024-01-19 11:09 ` David Marchand [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=CAJFAV8x6QFg-+CPMPYPzAiTz_3NFnGg9cz2fa0hfZ9oJJ3eJsw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--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).