From: randy_dunlap <rdunlap@xenotime.net>
To: Bodo Eggert <7eggert@gmx.de>
Cc: 7eggert@gmx.de, akpm@osdl.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [1/5+1] menu -> menuconfig part 1
Date: Thu, 21 Jul 2005 22:52:26 -0700 [thread overview]
Message-ID: <20050721225226.4fbd64f7.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0507171326470.6041@be1.lrz>
On Sun, 17 Jul 2005 13:29:03 +0200 (CEST) Bodo Eggert wrote:
> On Sun, 17 Jul 2005, Bodo Eggert wrote:
>
> > These patches change some menus into menuconfig options.
> >
> > Reworked to apply to linux-2.6.13-rc3-git3
>
> Mostly robotic works.
Hi,
When using xconfig (not menuconfig), the drivers/MTD menu
needs some help IMO, but it's not clear where/why.
Before the patch, there was only "Memory Technology
Devices (MTD)" in the left xconfig panel. After the patch,
under that heading there are 4 other MTD entries,
which are in the right-side panel before the patch and should
remain there. These are:
RAM/ROM/Flash chip drivers
Mapping drivers for chip access
Self-contained MTD device drivers
NAND Flash Device support
---
~Randy
next prev parent reply other threads:[~2005-07-22 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 11:12 [PATCH] [0/5+1] " Bodo Eggert
2005-07-17 11:29 ` [PATCH] [1/5+1] " Bodo Eggert
2005-07-17 17:03 ` [PATCH] [1b/5+1] " Bodo Eggert
2005-07-22 5:07 ` randy_dunlap
2005-07-22 9:37 ` [PATCH][RESEND] " Bodo Eggert
2005-07-22 5:52 ` randy_dunlap [this message]
2005-07-22 7:32 ` [PATCH] [1/5+1] " Jan Engelhardt
2005-07-24 9:50 ` Bodo Eggert
2005-07-22 6:11 ` randy_dunlap
2005-07-17 11:31 ` [PATCH] [2/5+1] " Bodo Eggert
2005-07-22 5:20 ` randy_dunlap
2005-07-17 11:32 ` [PATCH] [3/5+1] " Bodo Eggert
2005-07-17 11:33 ` [PATCH] [4/5+1] " Bodo Eggert
2005-07-17 11:36 ` [PATCH] [5/5+1] " Bodo Eggert
2005-07-17 11:39 ` [PATCH] [6/5+1] " Bodo Eggert
2005-07-17 13:45 ` [PATCH] [0/5+1] " Roman Zippel
2005-07-17 15:37 ` Bodo Eggert
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=20050721225226.4fbd64f7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®