public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: sam@ravnborg.org, linux-arch@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: add a top-level Networking menu to *config
Date: Tue, 12 Jul 2005 12:11:23 -0700 (PDT)	[thread overview]
Message-ID: <20050712.121123.39661217.davem@davemloft.net> (raw)
In-Reply-To: <20050708100211.5a1aebdf.rdunlap@xenotime.net>

From: randy_dunlap <rdunlap@xenotime.net>
Date: Fri, 8 Jul 2005 10:02:11 -0700

> 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 also think that there is some room for more consistency in
> the presentation of similar Network device categories, but
> maybe that (other) menuconfig patch will address this after
> your patch is merged, since that isn't what this patch was
> addressing.

Please provide a followon patch to make these changes,
as I put Sam's patches into my tree last night.

Thanks a lot.

  reply	other threads:[~2005-07-12 19:11 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 [this message]
2005-07-12 21:19   ` Sam Ravnborg
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=20050712.121123.39661217.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.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