From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] CONFIG_INET depend on CONFIG_SYSCTL
Date: Fri, 22 Jun 2007 16:42:31 +0900 [thread overview]
Message-ID: <m2lkecl9js.wl%ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20070612.230545.104645806.davem@davemloft.net>
At Tue, 12 Jun 2007 23:05:45 -0700 (PDT),
David Miller wrote:
>
> From: Yoshinori Sato <ysato@users.sourceforge.jp>
> Date: Wed, 13 Jun 2007 14:59:16 +0900
>
> > At Tue, 12 Jun 2007 01:08:55 -0700 (PDT),
> > David Miller wrote:
> >
> > > 2) It is much better to add the appropriate CONFIG_SYSCTL
> > > ifdefs to the INET code than to force it on for everyone.
> >
> > It examined that, but many corrections become necessary.
>
> I understand, but embedded people will not be happy that
> SYSFS is a requirement for IPV4 networking. Every little
> bit of space savings matters for them.
A reply became late, sorry.
I do not check it in detail, but there seem to be part a few
depending SYSFS.
I need to check whether can separate a SYSFS depending part.
It may take time, but tries to check it.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
prev parent reply other threads:[~2007-06-22 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2sl8xfwq8.wl%ysato@users.sourceforge.jp>
2007-06-12 8:08 ` [PATCH] CONFIG_INET depend on CONFIG_SYSCTL David Miller
2007-06-13 5:59 ` Yoshinori Sato
2007-06-13 6:05 ` David Miller
2007-06-22 7:42 ` Yoshinori Sato [this message]
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=m2lkecl9js.wl%ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).