DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Long Li <longli@microsoft.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/netvsc: fix log double spaced messages
Date: Thu, 8 Apr 2021 09:22:39 +0100	[thread overview]
Message-ID: <58196b45-e50d-ae87-99f1-2818b65a46c2@intel.com> (raw)
In-Reply-To: <BN8PR21MB11559D892CE936014012C1EDCE749@BN8PR21MB1155.namprd21.prod.outlook.com>

On 4/8/2021 3:03 AM, Long Li wrote:
>> -----Original Message-----
>> From: Stephen Hemminger <stephen@networkplumber.org>
>> Sent: Wednesday, April 7, 2021 7:01 PM
>> To: Long Li <longli@microsoft.com>
>> Cc: dev@dpdk.org; Stephen Hemminger <stephen@networkplumber.org>
>> Subject: [PATCH] net/netvsc: fix log double spaced messages
>>
>> The PMD_DRV_LOG macro in netvsc (like other drivers) adds a newline to
>> the log message as part of the macro expansion; therefore the message
>> should not have its own newline.
>>
>> In a couple places, log messages were split across source lines which can
>> make looking them up in the source tree harder.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> 
> Acked-by: Long Li <longli@microsoft.com>

     Fixes: a2a23a794b3a ("net/netvsc: support VF device hot add/remove")
     Cc: stable@dpdk.org

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2021-04-08  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08  2:00 Stephen Hemminger
2021-04-08  2:03 ` Long Li
2021-04-08  8:22   ` Ferruh Yigit [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=58196b45-e50d-ae87-99f1-2818b65a46c2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=longli@microsoft.com \
    --cc=stephen@networkplumber.org \
    /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).