All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [pull-request] next-eventdev 17.11 RC1
Date: Tue, 10 Oct 2017 23:42:29 +0530	[thread overview]
Message-ID: <20171010181229.GA9745@jerin> (raw)
In-Reply-To: <6833710.vh70Xgofij@xps>

-----Original Message-----
> Date: Tue, 10 Oct 2017 19:11:09 +0200
> From: Thomas Monjalon <thomas@monjalon.net>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [pull-request] next-eventdev 17.11 RC1
> 
> 10/10/2017 18:52, Jerin Jacob:
> > The following changes since commit 33604c31354abc9c55405d5a4b99eb42a55a495f:
> > 
> >   vfio: refactor PCI BAR mapping (2017-10-10 15:37:58 +0200)
> > 
> > are available in the git repository at:
> > 
> >   http://dpdk.org/git/next/dpdk-next-eventdev 
> 
> Thanks Jerin.
> 
> Please update patchwork when integrating patches.
> It is hard to understand the eventdev status currently:
> 	http://dpdk.org/dev/patchwork/project/dpdk/list/?delegate=310

I was in hurry to form pull request as you need it by end of today and
I thought to cleanup patchwork just after pushing the pull request.
Any way it done now.

http://dpdk.org/dev/patchwork/project/dpdk/list/?delegate=310 

Thanks for pointing out.


> 

  reply	other threads:[~2017-10-10 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 16:52 [pull-request] next-eventdev 17.11 RC1 Jerin Jacob
2017-10-10 17:11 ` Thomas Monjalon
2017-10-10 18:12   ` Jerin Jacob [this message]
2017-10-10 23:14 ` Thomas Monjalon

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=20171010181229.GA9745@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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.