From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: people <people@netdevconf.org>,
tech-committee <tech-committee@netdevconf.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Heri Muhero <hmuhero@gmail.com>,
netfilter <netfilter@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [NetDev] [Netdev ANNOUNCE]: New tc workshop accepted
Date: Mon, 20 Mar 2017 18:56:44 +0000 (UTC) [thread overview]
Message-ID: <747959804.19467.1490036204772.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <63339d3a-dcac-0639-2de0-204a773567dd@mojatatu.com>
Hi Jamal,
So, the interesting thing is that I've been automatically
re-subscribed to people@netdevconf.org about 1 day after
I explicitly unsubscribed. What do I need to do to stop
receiving those unsolicited emails ?
Best regards,
Mathieu
----- On Mar 20, 2017, at 1:32 PM, Jamal Hadi Salim jhs@mojatatu.com wrote:
> The tech committee would like to announce a new accepted workshop.
>
> Jamal Hadi Salim will chair the Traffic Control (tc) workshop
>
> Details are as follows:
> -----
> Face to Face discussions on different tc topics
>
> Current WAG agenda (subject to update):
>
> New tc offloads since netdev 1.2
> New features/requests/improvements
> Performance
> Packet edit/offload discussion
> YATO (Yet another Tunnel offload).
> ----
>
>
> cheers,
> jamal
>
> _______________________________________________
> people mailing list
> people@lists.netdevconf.org
> http://lists.netdevconf.org/cgi-bin/mailman/listinfo/people
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2017-03-20 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 17:32 [Netdev ANNOUNCE]: New tc workshop accepted Jamal Hadi Salim
2017-03-20 18:56 ` Mathieu Desnoyers [this message]
2017-03-20 19:54 ` [NetDev-tech] [NetDev] " Pablo Neira Ayuso
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=747959804.19467.1490036204772.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=hmuhero@gmail.com \
--cc=jhs@mojatatu.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=people@netdevconf.org \
--cc=tech-committee@netdevconf.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).