From: Daniel Borkmann <dborkman@redhat.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [PATCH net-next] net: vxlan: do not use vxlan_net before checking event type
Date: Sun, 19 Jan 2014 01:36:41 +0100 [thread overview]
Message-ID: <52DB1E19.5040909@redhat.com> (raw)
In-Reply-To: <CAM_iQpU6LW2a=kfryrvbZvUQ_+T_9n0dnoxEw_0G_J9hQfNHSQ@mail.gmail.com>
On 01/19/2014 12:48 AM, Cong Wang wrote:
> I do understand you want to be the author, next time, just tell me
> before you do, I will let you be whatever you want (if I can).
> That's all.
>
> REPEAT: I don't mind who fixes it, I DO mind you did it without
> asking me first.
Cong, I truly do __not__ care who is what or who isn't. I do care
that the code is fine. Sure, next time I'll ask, or better, just
give feedback; sorry for how this went, it was not my intention.
next prev parent reply other threads:[~2014-01-19 0:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 11:55 [PATCH net-next] net: vxlan: do not use vxlan_net before checking event type Daniel Borkmann
2014-01-17 17:30 ` Cong Wang
2014-01-17 18:32 ` Daniel Borkmann
2014-01-18 3:50 ` Cong Wang
2014-01-18 17:18 ` Eric Dumazet
2014-01-18 17:57 ` Cong Wang
2014-01-18 19:47 ` Daniel Borkmann
2014-01-18 23:32 ` Cong Wang
2014-01-18 23:48 ` Cong Wang
2014-01-19 0:36 ` Daniel Borkmann [this message]
2014-01-19 0:50 ` Cong Wang
[not found] ` <1390072047.31367.543.camel@edumazet-glaptop2.roam.corp.google.com>
2014-01-18 23:38 ` Cong Wang
2014-01-19 2:01 ` Eric Dumazet
2014-01-17 18:20 ` Jesse Brandeburg
2014-01-18 2:50 ` David Miller
2014-01-20 21:51 ` Eric W. Biederman
2014-01-20 22:01 ` Daniel Borkmann
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=52DB1E19.5040909@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 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.