All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] event/sw: remove spare newline from error logs
Date: Thu, 21 Sep 2017 15:35:18 +0530	[thread overview]
Message-ID: <20170921100517.GA23422@jerin> (raw)
In-Reply-To: <1505742140-63285-1-git-send-email-harry.van.haaren@intel.com>

-----Original Message-----
> Date: Mon, 18 Sep 2017 14:42:20 +0100
> From: Harry van Haaren <harry.van.haaren@intel.com>
> To: dev@dpdk.org
> CC: jerin.jacob@caviumnetworks.com, Harry van Haaren
>  <harry.van.haaren@intel.com>
> Subject: [PATCH] event/sw: remove spare newline from error logs
> X-Mailer: git-send-email 2.7.4
> 
> This commit removes extra newline characters from SW_LOG_ERR()
> messages, which cleans up the error output.
> 
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> 
> ---
> 
> Note that this patchset applies cleanly only on the updated service
> cores patchset (which contained a trivial change to SW PMD). Suggesting
> a rebase of next-eventdev tree before applying this - will make life easier :)
> 
> ---
>  drivers/event/sw/sw_evdev.c | 14 +++++++-------

drivers/event/sw/sw_evdev_xstats.c has similar instance.

➜ [dpdk-next-eventdev] $ grep -ri "SW_LOG_ERR" drivers/event/
drivers/event/sw/sw_evdev_xstats.c:		SW_LOG_ERR("Invalid mode received in sw_xstats_get_names()\n");
drivers/event/sw/sw_evdev_xstats.c:		SW_LOG_ERR("Invalid mode received in sw_xstats_get()\n");

      reply	other threads:[~2017-09-21 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 13:42 [PATCH] event/sw: remove spare newline from error logs Harry van Haaren
2017-09-21 10:05 ` Jerin Jacob [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=20170921100517.GA23422@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.