DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: fix incorrect MP/MC tail updates in rte_event_ring
Date: Wed, 4 Apr 2018 10:36:51 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA65E01DAA5@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20180404085218.GA5008@bricha3-MOBL.ger.corp.intel.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Wednesday, April 4, 2018 9:52 AM
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: Mattias Rönnblom <hofors@lysator.liu.se>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] eventdev: fix incorrect MP/MC tail updates in
> rte_event_ring
> 
> On Wed, Apr 04, 2018 at 06:22:26AM +0530, Jerin Jacob wrote:
> > -----Original Message-----
> > > Date: Tue, 3 Apr 2018 10:19:03 +0200
> > > From: Mattias Rönnblom <hofors@lysator.liu.se>
> > > To: dev@dpdk.org
> > > CC: jerin.jacob@caviumnetworks.com, Mattias Rönnblom
> > >  <hofors@lysator.liu.se>, bruce.richardson@intel.com
> > > Subject: [PATCH] eventdev: fix incorrect MP/MC tail updates in
> > >  rte_event_ring
> > > X-Mailer: git-send-email 2.7.4
> > >
> > > rte_event_ring enqueue and dequeue tail updates were hardcoded for a
> > > SC/SP configuration.
> > >
> > > Fixes: dc39e2f359b5 ("eventdev: add ring structure for events")
> > > Cc: bruce.richardson@intel.com

Hi Mattias,

I think this is a v2 of the patch here:
http://dpdk.org/dev/patchwork/patch/36604/

When doing the git-send-email, we should pass the -v2 parameter, so the subject says [PATCH v2].
It is helpful to CC the people who replied to the V1 of the patch, so they are aware of the re-submit.

Bruce has Acked this patch, so it can be merged now - above is just for future reference.

Regards, -Harry

<snip>

      parent reply	other threads:[~2018-04-04 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  9:16 Mattias Rönnblom
2018-03-29 12:38 ` Van Haaren, Harry
2018-04-02  2:55   ` Jerin Jacob
2018-04-03  8:14   ` Mattias Rönnblom
2018-04-03  8:19 ` Mattias Rönnblom
2018-04-04  0:52   ` Jerin Jacob
2018-04-04  8:52     ` Bruce Richardson
2018-04-04  9:46       ` Jerin Jacob
2018-04-04 10:36       ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA65E01DAA5@IRSMSX101.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hofors@lysator.liu.se \
    --cc=jerin.jacob@caviumnetworks.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).