DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Marchetti <mmarchetti@sandvine.com>
To: "O'driscoll, Tim" <tim.o'driscoll@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Community Conference Call - Friday 31st October
Date: Fri, 24 Oct 2014 15:05:55 +0000	[thread overview]
Message-ID: <A7E5BBF1ACE50B43AF1D6E89B8280FE4C52C3DD0@wtl-exchp-1.sandvine.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C42C29@IRSMSX102.ger.corp.intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'driscoll, Tim
> Sent: Friday, October 24, 2014 5:22 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] DPDK Community Conference Call - Friday 31st October
> 
> We're planning to hold our first community conference call on Friday 31st
> October. It's impossible to find a time that suits everybody, so we've chosen
> to do this in the afternoon/evening in Europe, which is the morning in the
> USA. This does unfortunately limit participation from PRC, Japan and other
> parts of the world. Here's the time and date in a variety of time zones:
> 
> Dublin (Ireland)				Friday, October 31, 2014 at
> 4:00:00 PM    GMT UTC
> Paris (France)				Friday, October 31, 2014 at 5:00:00
> PM    CET UTC+1 hour
> San Francisco (U.S.A. - California)	Friday, October 31, 2014 at 9:00:00
> AM    PDT UTC-7 hours
> New York (U.S.A. - New York)		Friday, October 31, 2014 at 12:00:00
> Noon EDT UTC-4 hours
> Tel Aviv (Israel)				Friday, October 31, 2014 at 6:00:00
> PM    IST UTC+2 hours
> Moscow (Russia)			Friday, October 31, 2014 at 7:00:00
> PM    MSK UTC+3 hours
> 
> 
> Audio bridge details are:
> France:		+33 1588 77298
> Germany:	+49 8999 143191
> Israel:		+972 2589 6577
> Russia: 		+7 495 641 4663
> UK:		+44 1793 402663
> USA:		+1 916 356 2663
> 
> Bridge: 5
> Conference ID: 1264677285
> 
> If anybody needs an access number for another country, let me know.

Can you provide a number for Canada?  thanks, Mike.


> 
> 
> Agenda:
> Discuss feature list for DPDK 2.0 (Q1 2015).
> Suggestions for topics for future calls.
> 
> 
> Thanks,
> Tim

  reply	other threads:[~2014-10-24 14:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  9:22 O'driscoll, Tim
2014-10-24 15:05 ` Michael Marchetti [this message]
2014-10-24 15:22   ` O'driscoll, Tim
2014-10-31 15:34 ` O'driscoll, Tim
2014-10-31 17:36   ` O'driscoll, Tim
2014-11-01 12:59     ` Neil Horman
2014-11-01 14:05       ` Vincent JARDIN
2014-11-05 13:00     ` [dpdk-dev] bifurcated driver Thomas Monjalon
2014-11-05 15:14       ` Alex Markuze
2014-11-05 15:19         ` Alex Markuze
2014-11-05 22:19           ` Zhou, Danny
2014-11-05 22:48       ` Zhou, Danny
2014-11-06  1:30         ` Vincent JARDIN
2014-11-06  4:45           ` Zhou, Danny
2014-11-06  8:13             ` Alex Markuze
2014-11-06  9:10               ` Nicolas Dichtel
2014-11-24 11:57       ` Luke Gorrie
2014-11-24 13:38         ` Zhou, Danny
2014-11-20  7:17     ` [dpdk-dev] DPDK Community Conference Call - Friday 31st October Kevin Wilson
2014-11-20 13:13       ` O'driscoll, Tim
2014-11-20 17:02         ` Kevin Wilson
2014-11-20 23:26           ` O'driscoll, Tim
2014-11-21 10:54             ` Kevin Wilson

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=A7E5BBF1ACE50B43AF1D6E89B8280FE4C52C3DD0@wtl-exchp-1.sandvine.com \
    --to=mmarchetti@sandvine.com \
    --cc=dev@dpdk.org \
    --cc=tim.o'driscoll@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 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).