From: Sergei Shtylyov <sergei.shtylyov@cogentembedded•com>
To: "Bjørn Mork" <bjorn@mork•no>
Cc: sunil.kovvuri@gmail•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org, sgoutham@cavium•com,
robert.richter@caviumnetworks•com,
Robert Richter <rrichter@cavium•com>
Subject: Re: [PATCH 5/6] net: thunderx: bgx: Add log message when setting mac address
Date: Mon, 8 Feb 2016 16:51:22 +0300 [thread overview]
Message-ID: <56B89D5A.8070503@cogentembedded.com> (raw)
In-Reply-To: <87vb5z1fd6.fsf@nemi.mork.no>
On 02/08/2016 04:49 PM, Bjørn Mork wrote:
>> dev_er(), maybe?
>
> I like that!
>
> It's often hard to know whether to print something or be quiet.
> pr_er(), dev_er(), netdev_er() etc would be the perfect solution to that
> problem.
:-D
Sorry for the typo...
> Bjørn
MBR, Sergei
next prev parent reply other threads:[~2016-02-08 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 12:07 [PATCH 0/6] net: thunderx: Setting IRQ affinity hints and other optimizations sunil.kovvuri
2016-02-08 12:07 ` [PATCH 1/6] net, thunderx: Add TX timeout and RX buffer alloc failure stats sunil.kovvuri
2016-02-08 12:07 ` [PATCH 2/6] net: thunderx: Use napi_schedule_irqoff() sunil.kovvuri
2016-02-08 12:07 ` [PATCH 3/6] net: thunderx: Assign affinity hints to vf's interrupts sunil.kovvuri
2016-02-08 12:07 ` [PATCH 4/6] net: thunderx: bgx: Use standard firmware node infrastructure sunil.kovvuri
2016-02-08 12:07 ` [PATCH 5/6] net: thunderx: bgx: Add log message when setting mac address sunil.kovvuri
2016-02-08 13:30 ` Sergei Shtylyov
2016-02-08 13:48 ` Robert Richter
2016-02-08 13:49 ` Bjørn Mork
2016-02-08 13:51 ` Sergei Shtylyov [this message]
2016-02-08 12:07 ` [PATCH 6/6] net: thunderx: Alloc higher order pages when pagesize is small sunil.kovvuri
2016-02-11 13:26 ` [PATCH 0/6] net: thunderx: Setting IRQ affinity hints and other optimizations Sunil Kovvuri
2016-02-11 14:33 ` David Miller
2016-02-11 15:12 ` Robert Richter
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=56B89D5A.8070503@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded$(echo .)com \
--cc=bjorn@mork$(echo .)no \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=robert.richter@caviumnetworks$(echo .)com \
--cc=rrichter@cavium$(echo .)com \
--cc=sgoutham@cavium$(echo .)com \
--cc=sunil.kovvuri@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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