From: Tomas Szepe <szepe@pinerecords.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [PATCH,RFC] move CONFIG_NET to net/Kconfig
Date: Wed, 1 Jan 2003 22:55:41 +0100 [thread overview]
Message-ID: <20030101215541.GF17053@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301011345100.12809-100000@home.transmeta.com>
> [torvalds@transmeta.com]
> >
> > > The best part of this patch is that it eliminates a lot of duplicit
> > > stuff in 15 arch-specific files (only sparc32 and m68k define their
> > > net devices in an arch specific Kconfig) and places a single 'source
> > > "drivers/net/Kconfig"' line in the one file where it belongs, net/Kconfig.
> >
> > Of course I could move sparc32 and m68k specific net devices to
> > drivers/net/Kconfig as well.
>
> I really think that's the only reasonable option. Please talk to Davem
> about getting the resuling sparc problems fixed up (it probably entails
> making sure that all the network drivers have the proper dependencies on
> PCI and ISA etc).
Yes, I'm working on that at the moment. Pete Zaitcev likes the idea and
DaveM won't probably hate it either, as that's how sparc64 has always been.
I'll carry on with this as soon as sparclinux people ack the resulting patch.
I have no clue about m68k whatsoever.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-01 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 19:32 Tomas Szepe
2003-01-01 20:43 ` Tomas Szepe
2003-01-01 21:46 ` Linus Torvalds
2003-01-01 21:55 ` Tomas Szepe [this message]
2003-01-01 23:18 ` David S. Miller
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=20030101215541.GF17053@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome