public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: linux-arch@vger.kernel.org, netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH 1/2] net: add a top-level Networking menu to *config
Date: Tue, 12 Jul 2005 21:19:42 +0000	[thread overview]
Message-ID: <20050712211942.GA9972@mars.ravnborg.org> (raw)
In-Reply-To: <20050708100211.5a1aebdf.rdunlap@xenotime.net>

> 
> Hi Sam,
> 
> I tested this on 2.6.13-rc2, using menuconfig, xconfig, and
> gconfig, with various ARCH=arches.
Thanks!

> Looking good to me, but I have one small change request.
> 
> Can the NETPOLL options that are under
>   Networking support  + Networking options
> (that depend on NETCONSOLE) and the NETCONSOLE option that is under
>   Device Drivers + Network device support
> be moved to the same area?  I don't really care which area,
> but it's a hassle to have to move between them to enable/disable
> them.
I would be glad if you could do this patch. You have better net/
knowledge than I do - and now that Davem applied my patch it should be
a much less intrusive patch to rearrange net/Kconfig.
It would be fine if you could address some of the other inconsistencies
too.

	Sam

  parent reply	other threads:[~2005-07-12 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  0:38 [PATCH 1/2] net: add a top-level Networking menu to *config Sam Ravnborg
2005-07-08  0:43 ` [PATCH 2/2] net: move config options out to individual protocols Sam Ravnborg
2005-07-12 19:10   ` David S. Miller
2005-07-08 17:02 ` [PATCH 1/2] net: add a top-level Networking menu to *config randy_dunlap
2005-07-12 19:11   ` David S. Miller
2005-07-12 21:19   ` Sam Ravnborg [this message]
2005-07-13  4:24     ` randy_dunlap
2005-07-12 19:10 ` 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=20050712211942.GA9972@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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