From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Patch to patchin.sh file
Date: Tue, 26 Jun 2001 16:52:24 -0500 [thread overview]
Message-ID: <3B390418.8957E048@daniel.com> (raw)
Any reason the following patch to the file patches/patchin.sh should not
be applied to the file in CVS?
It adds the JFFS2 dir/file/include stuff to a stock kernel that knows
nothing about it.
Vipin
Index: patchin.sh
===================================================================
RCS file: /home/cvs/mtd/patches/patchin.sh,v
retrieving revision 1.6
diff -u -r1.6 patchin.sh
--- patchin.sh 2001/04/25 12:10:23 1.6
+++ patchin.sh 2001/06/26 21:40:06
@@ -24,12 +24,16 @@
#
mkdir -p drivers/mtd
+rm -rf drivers/mtd/* # clear out old junk
mkdir -p drivers/mtd/chips
mkdir -p drivers/mtd/devices
mkdir -p drivers/mtd/maps
mkdir -p drivers/mtd/nand
mkdir -p include/linux/mtd
mkdir -p fs/jffs
+rm -rf fs/jffs/* # clear out old junk
+mkdir -p fs/jffs2
+rm -rf fs/jffs2/* # clear out old junk
ln -sf $TOPDIR/drivers/mtd/*.[ch] drivers/mtd
ln -sf $TOPDIR/drivers/mtd/*akefile $TOPDIR/drivers/mtd/Rules.make
$TOPDIR/drivers/mtd/Config.in drivers/mtd
ln -sf $TOPDIR/drivers/mtd/chips/*.[ch] drivers/mtd/chips
@@ -42,7 +46,10 @@
ln -sf $TOPDIR/drivers/mtd/nand/*akefile
$TOPDIR/drivers/mtd/nand/Config.in drivers/mtd/nand
ln -sf $TOPDIR/fs/jffs/*.[ch] fs/jffs
ln -sf $TOPDIR/fs/jffs/*akefile fs/jffs
-ln -sf $TOPDIR/include/linux/jffs.h include/linux
+ln -sf $TOPDIR/fs/jffs2/*.[ch] fs/jffs2
+ln -sf $TOPDIR/fs/jffs2/*akefile fs/jffs2
+#ln -sf $TOPDIR/include/linux/jffs.h include/linux
+ln -sf $TOPDIR/include/linux/jffs*.h include/linux
ln -sf $TOPDIR/include/linux/mtd/*.h include/linux/mtd
#
reply other threads:[~2001-06-26 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B390418.8957E048@daniel.com \
--to=vipin.malik@daniel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.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