From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Ranjit Menon <ranjit.menon@intel.com>,
cathal.ohare@intel.com, harini.ramakrishnan@microsoft.com,
pallavi.kadam@intel.com, bruce.richardson@intel.com,
rasland@mellanox.com, Adham Masarwah <adham@mellanox.com>,
Eilon Greenstein <eilong@mellanox.com>,
Anan Saif <anans@mellanox.com>,
Rani Sharoni <ranish@mellanox.com>,
Yohad Tor <yohadt@mellanox.com>,
Omar Cardona <ocardona@microsoft.com>,
Haseeb.Gani@cavium.com, shshaikh@marvell.com,
nareshkumar.pbs@broadcom.com,
Tal Shnaiderman <talshn@mellanox.com>
Subject: Re: [dpdk-dev] DPDK Windows Community call - 02 May 2019
Date: Thu, 16 May 2019 15:10:21 +0200 [thread overview]
Message-ID: <1935548.CojDo964dP@xps> (raw)
In-Reply-To: <3423275.GdfnmaGHQd@xps>
sending again with fixed Cc list
16/05/2019 11:41, Thomas Monjalon:
> 14/05/2019 17:48, Thomas Monjalon:
> > 10/05/2019 01:34, Ranjit Menon:
> > > Contact Cathal to be added to this meeting invite.
> >
> > Would it be possible to move this bi-weekly meeting
> > to the Tuesday (same time), please?
> >
> > [...]
> > > Encourage other dpdk.org Windows partners to join this call.
> >
> > Yes, would be nice to hear more developers joining the party.
> >
> [...]
> > What is the status of the PCI code in drivers/bus/pci?
> > Is someone working on it with clang and meson?
> > Mellanox would like to join the effort on PCI.
>
> Please add the Mellanox engineers who are Cc of this mail.
> Mellanox is ramping up. We need to know how to proceed with the PCI code.
prev parent reply other threads:[~2019-05-16 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 23:34 Ranjit Menon
2019-05-09 23:34 ` Ranjit Menon
2019-05-14 15:48 ` Thomas Monjalon
2019-05-14 15:48 ` Thomas Monjalon
2019-05-14 16:52 ` Harini Ramakrishnan
2019-05-14 16:52 ` Harini Ramakrishnan
2019-05-16 9:41 ` Thomas Monjalon
2019-05-16 9:41 ` Thomas Monjalon
2019-05-16 13:10 ` 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=1935548.CojDo964dP@xps \
--to=thomas@monjalon.net \
--cc=Haseeb.Gani@cavium.com \
--cc=adham@mellanox.com \
--cc=anans@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=cathal.ohare@intel.com \
--cc=dev@dpdk.org \
--cc=eilong@mellanox.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=nareshkumar.pbs@broadcom.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranish@mellanox.com \
--cc=ranjit.menon@intel.com \
--cc=rasland@mellanox.com \
--cc=shshaikh@marvell.com \
--cc=talshn@mellanox.com \
--cc=yohadt@mellanox.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).