From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: events@dpdk.org, sujata.tibrewala@intel.com
Subject: [dpdk-web] [PATCH] update India summit
Date: Tue, 6 Feb 2018 03:04:31 +0100 [thread overview]
Message-ID: <20180206020431.20098-1-thomas@monjalon.net> (raw)
Add an introduction to the event and remove closed CfP.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
events.html | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/events.html b/events.html
index 6555fd8..8a97128 100644
--- a/events.html
+++ b/events.html
@@ -40,15 +40,21 @@
</header>
<section id="events">
<h2 id="indiasummit2018">› DPDK <em>Summit</em>, Bangalore - March 9, 2018</h2>
+ <p>The first DPDK Summit of 2018 will take place in the
+ <a href="https://theleela.com/en_us/hotels-in-bengaluru/the-leela-palace-hotel-bengaluru/">Leela Palace hotel</a>
+ in Bangalore on Friday March 9th.</p>
+ <p>The event will cover the latest developments to the DPDK framework,
+ and their application to a variety of industry segments
+ including telecom, cloud, enterprise and security.
+ The event enables the DPDK open source community to share information
+ on DPDK usage and implementation;
+ to hear from DPDK developers, contributors, and users;
+ and to build the DPDK community.</p>
<p style="text-align: center;">
<a href="https://www.regonline.com/DPDKBangalore2018" class="button">
<i class="material-icons">event_note</i>
Register
</a>
- <a href="https://goo.gl/forms/Xp1YFG86oUdpOSoi2" class="button">
- <i class="material-icons">create</i>
- Call for Proposal
- </a>
</p>
<h3 id="usasummit2017">› DPDK <em>Summit</em>, San Jose - November 14-15, 2017</h3>
<p>
--
2.15.1
next reply other threads:[~2018-02-06 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 2:04 Thomas Monjalon [this message]
2018-02-06 10:14 ` Mcnamara, John
2018-02-06 10:31 ` Thomas Monjalon
2018-02-06 23:31 ` Tibrewala, Sujata
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=20180206020431.20098-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=events@dpdk.org \
--cc=sujata.tibrewala@intel.com \
--cc=web@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).