patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: stable@dpdk.org, "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	dev@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] service: fix number mapped cores count
Date: Thu, 11 Jan 2018 23:24:50 +0100	[thread overview]
Message-ID: <1667114.nidiDLP3DL@xps> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA650FEBCF5@IRSMSX102.ger.corp.intel.com>

> > When adding service the number of mapped cores should only be incremented
> > when the core is not already a service core or vice versa.
> > 
> > Fixes: 21698354c832 ("service: introduce service cores concept")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> 
> Just a note;
> Be careful of going more than 75 chars on git commit messages,
> 
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>

Applied, thanks

      reply	other threads:[~2018-01-11 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180109094041.5148-1-pbhagavatula@caviumnetworks.com>
2018-01-09 11:44 ` Van Haaren, Harry
2018-01-11 22:24   ` Thomas Monjalon [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=1667114.nidiDLP3DL@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=stable@dpdk.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).