netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Chen <wangchen@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: kaber@trash.net, netdev@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: v4 [PATCH 9/9] 8021q: Check return of dev_set_promiscuity/allmulti
Date: Tue, 15 Jul 2008 14:04:47 +0800	[thread overview]
Message-ID: <487C3DFF.1050809@cn.fujitsu.com> (raw)
In-Reply-To: <20080714.210056.47426171.davem@davemloft.net>

David Miller said the following on 2008-7-15 12:00:
> But I had to apply this one also by hand, as it conflicted with
> Patrick's GVRP changes already in the tree.
> 

Sorry*2 for making you typing my patch twice. ;)

> When you are maintaining a patch set like this, you have to update
> your tree and regenerate your patches in order to make sure no new
> conflicts exist before submitting your patches.
> 
> That part isn't my job :)
> 
> Thanks.

OK.
But I need some help from you, otherwise the latest tree to me is Linus's
mainline tree.
Actually, long time ago, I want to git-clone your net tree but failed.
But I can git-clone Linus's.
The reason is that in my working place I can only use http protocol when git
clone. But your tree seems not work for http git-clone.
I asked Herbert before, he said, maybe git-update-server-info needs to be
executed.
I am very appreciated if you can figure out why net tree can't be cloned by http.
And maybe there are some other people whose employer's firewall filtering git
port.
Thank you for your understanding in advance :)


  reply	other threads:[~2008-07-15  6:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <487C0ABA.1070506@cn.fujitsu.com>
2008-07-15  2:59 ` v4 [PATCH 1/9] af_packet: Check return of dev_set_promiscuity/allmulti Wang Chen
2008-07-15  3:51   ` David Miller
2008-07-15  7:52     ` [PATCH] af_packet: po->mclist needs locker in reader side(WAS: [PATCH 1/9] af_packet: Check return of dev_set_promiscuity/allmulti) Wang Chen
2008-07-15  9:11       ` [PATCH] af_packet: po->mclist needs locker in reader side David Miller
2008-07-15 10:32         ` Wang Chen
2008-07-15  2:59 ` v4 [PATCH 2/9] bonding: Check return of dev_set_promiscuity/allmulti Wang Chen
2008-07-15  3:51   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 3/9] bridge: Check return of dev_set_promiscuity Wang Chen
2008-07-15  3:54   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 4/9] ipv6: Check return of dev_set_allmulti Wang Chen
2008-07-15  3:54   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 5/9] ipv6: Fix using after dev_put() Wang Chen
2008-07-15  3:55   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 6/9] ipv4: Check return of dev_set_allmulti Wang Chen
2008-07-15  3:55   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 7/9] ipv4: Fix ipmr unregister device oops Wang Chen
2008-07-15  3:56   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 8/9] macvlan: Check return of dev_set_allmulti Wang Chen
2008-07-15  3:57   ` David Miller
2008-07-15  2:59 ` v4 [PATCH 9/9] 8021q: Check return of dev_set_promiscuity/allmulti Wang Chen
2008-07-15  4:00   ` David Miller
2008-07-15  6:04     ` Wang Chen [this message]
2008-07-17  5:41       ` git clone net-next-2.6 Wang Chen

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=487C3DFF.1050809@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.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 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).