netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [Patch net-next] ipv6: separate out procfs code from mcast.c
Date: Tue, 23 Apr 2013 15:15:02 +0800	[thread overview]
Message-ID: <1366701302.21136.19.camel@cr0> (raw)
In-Reply-To: <20130423.031135.166163672665280174.davem@davemloft.net>

On Tue, 2013-04-23 at 03:11 -0400, David Miller wrote:
> From: Cong Wang <amwang@redhat.com>
> Date: Tue, 23 Apr 2013 15:07:00 +0800
> 
> > From: Cong Wang <amwang@redhat.com>
> > 
> > They well deserve a separated unit.
> > 
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org> 
> > Signed-off-by: Cong Wang <amwang@redhat.com>
> 
> Cong, I'm not even reading these patches.
> 
> You're on this idea that you can just keep the sysfs and procfs bits
> of ipv6 modular, and make the rest of ipv6 statically linked into the
> kernel.

I am trying that only for mcast.c, not for the whole IPv6.

  reply	other threads:[~2013-04-23  7:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  7:07 [Patch net-next] ipv6: separate out procfs code from mcast.c Cong Wang
2013-04-23  7:11 ` David Miller
2013-04-23  7:15   ` Cong Wang [this message]
2013-04-23  7:18     ` David Miller
2013-04-23  7:30       ` Cong Wang
2013-04-23  7:36         ` David Miller
2013-04-23  7:41           ` Cong Wang
2013-04-23 12:33             ` Bjørn Mork
2013-04-23 16:13               ` Ben Hutchings
2013-04-24  3:33                 ` Cong Wang
2013-04-23 17:26               ` David Stevens
2013-04-24  5:26                 ` Cong Wang
2013-04-24  3:29               ` Cong Wang

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=1366701302.21136.19.camel@cr0 \
    --to=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).