From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH] enic: silence log message
Date: Mon, 9 Feb 2015 08:11:14 -0800 [thread overview]
Message-ID: <CAOaVG17Zjw1S+rG3pMh2eGjYGaD6tQw6-4zETU-dW=MpPsmoGg@mail.gmail.com> (raw)
In-Reply-To: <CALwxeUt87snj1=fbc4UyV9fbR_aYUN5FmU2v7tF3CBrk4M3OEQ@mail.gmail.com>
Agree it should not use printf.
If you insist on keeping the useless message then it should be log level
debug
next prev parent reply other threads:[~2015-02-09 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 17:36 Stephen Hemminger
2015-02-08 17:36 ` Stephen Hemminger
2015-02-09 12:21 ` David Marchand
2015-02-09 16:11 ` Stephen Hemminger [this message]
2015-02-15 6:13 ` Sujith Sankar (ssujith)
2015-02-15 6:29 ` Sujith Sankar (ssujith)
-- strict thread matches above, loose matches on Subject: below --
2015-02-08 17:35 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='CAOaVG17Zjw1S+rG3pMh2eGjYGaD6tQw6-4zETU-dW=MpPsmoGg@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.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;
as well as URLs for NNTP newsgroup(s).