From: Erwin Authried <eauth@softsys.co.at>
To: "'mtd@infradead.org'" <mtd@infradead.org>
Subject: MTD patches for 2.0 / 2.2 kernels
Date: Wed, 31 Jan 2001 12:35:47 +0100 [thread overview]
Message-ID: <01C08B82.5716DF60@smithwicks.softsys.co.at> (raw)
I took a look at the "patches" directory and recognized that
the patches that are available via ftp have the complete mtd
tree included. Wouldn' t it be much nicer to have a patch
script (like patchin.sh), that
1. makes symlinks from the kernel source into the mtd tree,
and 2. applies a very small patch for the kernel source
(init/main.c, drivers/Makefile, ...)
I think that would be much more maintainable and easier to
use than the seperate patches from the ftp server. It could even
be reduced to invoke the patch script with the path to the
kernel source, and the script might retrieve the version from
there to apply the correct patch. I'd like to see all the patches
inside the CVS distribution, instead of having them to download
via ftp seperately.
Is there a special reason why there is a seperate link for
each mtd source file in patchin.sh, instead of having just one
symbolic link for the mtd directory? This way, the kernel would
still be compileable if files are added to the mtd directory,
without having to care about the symlinks.
-Erwin
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2001-01-31 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 11:35 Erwin Authried [this message]
2001-01-31 12:03 ` MTD patches for 2.0 / 2.2 kernels David Woodhouse
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=01C08B82.5716DF60@smithwicks.softsys.co.at \
--to=eauth@softsys.co.at \
--cc=mtd@infradead.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