From: Raphael Hertzog <eng@eipm.ch>
To: Stephane List <stephane.list@lilotux.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Intel Strataflash
Date: 30 Jan 2003 12:00:44 +0100 [thread overview]
Message-ID: <1043924444.555.30.camel@localhost> (raw)
In-Reply-To: <20030130094658.GB11189@lilotux.net>
Am Don, 2003-01-30 um 10.46 schrieb Stephane List:
> On mer, jan 29, 2003 at 10:36:13 +0000,
> David Woodhouse <dwmw2@infradead.org> wrote:
> > On Wed, 29 Jan 2003, Stephane List wrote:
> >
> > > PS : I couldn't compile my kernel with the CVS code...
> >
> > Details?
> >
>
> my grep doesn't know the "-m option" so I think that the patch isn't correctly applied.
> I will look at "patchin.sh" to correct this.
Here's the patch that I use (if someone wants to commit it ...) :
Index: patchin.sh
===================================================================
RCS file: /home/cvs/mtd/patches/patchin.sh,v
retrieving revision 1.9
diff -u -r1.9 patchin.sh
--- patchin.sh 30 Nov 2002 23:48:39 -0000 1.9
+++ patchin.sh 30 Jan 2003 10:57:18 -0000
@@ -60,9 +60,9 @@
fi
# Get kernel version
-VERSION=`grep -sm 1 VERSION <$LINUXDIR/Makefile | sed s/'VERSION = '//`
-PATCHLEVEL=`grep -sm 1 PATCHLEVEL <$LINUXDIR/Makefile | sed s/'PATCHLEVEL = '//`
-SUBLEVEL=`grep -sm 1 SUBLEVEL <$LINUXDIR/Makefile | sed s/'SUBLEVEL = '//`
+VERSION=`grep ^VERSION $LINUXDIR/Makefile | sed s/'VERSION = '//`
+PATCHLEVEL=`grep ^PATCHLEVEL $LINUXDIR/Makefile | sed s/'PATCHLEVEL = '//`
+SUBLEVEL=`grep ^SUBLEVEL $LINUXDIR/Makefile | sed s/'SUBLEVEL = '//`
# Can we handle this ?
if test $VERSION -ne 2 -o $PATCHLEVEL -lt 4
Cheers,
--
Raphaël Hertzog - EIPM SA
next prev parent reply other threads:[~2003-01-30 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 16:14 Intel Strataflash Stephane List
2003-01-29 22:36 ` David Woodhouse
2003-01-30 9:46 ` Stephane List
2003-01-30 11:00 ` Raphael Hertzog [this message]
2003-01-30 10:18 ` Stephane List
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=1043924444.555.30.camel@localhost \
--to=eng@eipm.ch \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=stephane.list@lilotux.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