From: Bernhard Priewasser <priewasser@gmail.com>
To: kyungmin.park@samsung.com, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] OneNAND: Simple Bad Block handling support
Date: Wed, 24 Aug 2005 11:24:46 +0200 [thread overview]
Message-ID: <430C3CDE.5020008@gmail.com> (raw)
In-Reply-To: <0ILP000HJ8JG7E@mmp1.samsung.com>
> Which directory are you patch? MTD-CVS or kernel?
I ran it outside the kernel tree:
[...]/mtd/> patch -p1 onenand-bbm.patch
Trying it inside the kernel tree results in the same errors:
/usr/src/linux> patch -p1 /[...]/mtd/onenand-bbm.patch
> 1. patching onenand-syncread.patch (check previous e-mail)
> 2. onenand-bbm.patch
> 3. omap-onenand.patch
This order works better in some way: fewer fails :-) But errors anyway.
Did you try to apply the patches? In which way exactly? Applying them in
the correct order helps a bit, but I can't see any difference between
inside/outside kernel tree. Should I?...
But I'm not sure, because:
> Perhaps it's a silly fault... I'm new to diff/patch, sorry.
:-)
Ah, one thing: inline mail attaching onenand-syncread.patch causes some
incorrect line wrappings which have to be corrected manually before
running patch. Perhaps it would be better to send them really as .patch
files.
Regards,
Bernhard
next prev parent reply other threads:[~2005-08-24 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 8:16 [PATCH] OneNAND: Simple Bad Block handling support Kyungmin Park
2005-08-23 13:56 ` Bernhard Priewasser
2005-08-23 23:42 ` Kyungmin Park
2005-08-24 9:24 ` Bernhard Priewasser [this message]
2005-08-24 10:49 ` Bernhard Priewasser
2005-08-24 23:36 ` Kyungmin Park
2005-08-25 7:56 ` Bernhard Priewasser
2005-09-01 9:30 ` Bernhard Priewasser
2005-09-01 10:03 ` Kyungmin Park
2005-09-01 10:09 ` Bernhard Priewasser
2005-09-07 8:09 ` Bernhard Priewasser
2005-09-07 11:44 ` Kyungmin Park
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=430C3CDE.5020008@gmail.com \
--to=priewasser@gmail.com \
--cc=kyungmin.park@samsung.com \
--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