From: Cong Wang <amwang@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [Patch net-next v9 00/11] vxlan: add ipv6 support
Date: Tue, 28 May 2013 10:42:58 +0800 [thread overview]
Message-ID: <1369708978.8181.39.camel@cr0> (raw)
In-Reply-To: <87ehcsbmfk.fsf@nemi.mork.no>
On Mon, 2013-05-27 at 15:07 +0200, Bjørn Mork wrote:
> Cong Wang <amwang@redhat.com> writes:
>
> > On Mon, 2013-05-27 at 02:30 -0700, David Miller wrote:
> >>
> >> And you had the nerve to complain when we were unwilling to merge this
> >> not-ready garbage into 3.10?!?! Are you kidding me?
> >
> > Please fix the netfilter erorrs too:
> >
> > http://marc.info/?l=netfilter-devel&m=136849956816787&w=2
> >
> > which were reported by me two weeks ago, NO ONE cares!
>
> I am pretty sure you are wrong about that.
It is true that no one replies to my report, maybe someone fixed it
without Cc'ing me, but how could I know that since my RH email doesn't
subscribe any mailing list.
>
> > Just complaining about vxlan seems unfair. :)
>
> Would you prefer that I didn't report this bug? Do you believe the
> existence of other bugs means that you don't need to test your patches?
> Are your for real?
Obviously no, you take a wrong point.
My point is you should care other IPV6=m errors as much as you care for
vxlan ones. I don't see any reply from you when I reported the netfilter
errors, even after two weeks! For me this sounds like you are ignoring
them on purpose, although I don't mind...
>
> Give me one reason why I should bother even looking at your next
> submission. Just to make it clear: No comments from me the next time
> you post this set only means that I didn't test it. Which seems
> likely given your ability to take any feedback at all.
You said "I see that you don't bother listen to advice", this is
OBVIOUSLY not true, I really did compile with three different configs,
just due a stupid mistake I took my IPV6=n config as IPV6=m config.
Your conclusion like this one is really offending, and I can't see any
respect for my work from your reply.
I am sorry for my mistake, and I always welcome for any feedbacks, but
just please be with respect. If next time I still see offending reply
like this, I will just ignore you. Sorry, but this is my right. :(
next prev parent reply other threads:[~2013-05-28 2:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 4:16 [Patch net-next v9 00/11] vxlan: add ipv6 support Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 01/11] vxlan: defer vxlan init as late as possible Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 02/11] vxlan: use unsigned int instead of unsigned Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 03/11] ipv6: make ip6_dst_hoplimit() static inline Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 04/11] ipv6: move ip6_local_out into core kernel Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 05/11] ipv6: export a stub for IPv6 symbols used by vxlan Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 06/11] ipv6: export in6addr_loopback to modules Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 07/11] vxlan: add ipv6 support Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 08/11] vxlan: add ipv6 route short circuit support Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 09/11] vxlan: add ipv6 proxy support Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 10/11] vxlan: respect scope_id for ll addr Cong Wang
2013-05-27 4:16 ` [Patch net-next v9 11/11] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-05-27 8:39 ` [Patch net-next v9 00/11] vxlan: add ipv6 support Bjørn Mork
2013-05-27 8:57 ` Bjørn Mork
2013-05-27 9:30 ` David Miller
2013-05-27 10:54 ` Cong Wang
2013-05-27 11:12 ` Cong Wang
2013-05-27 11:00 ` Cong Wang
2013-05-27 13:07 ` Bjørn Mork
2013-05-28 2:42 ` Cong Wang [this message]
2013-05-28 7:28 ` Bjørn Mork
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=1369708978.8181.39.camel@cr0 \
--to=amwang@redhat.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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.