From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Detlev Zundel <dzu@denx.de>
Subject: Re: [PATCH] mtdchar: allow mmap() on MTD RAM/ROM char devices
Date: Wed, 28 Apr 2010 16:31:58 +0300 [thread overview]
Message-ID: <1272461518.7750.31.camel@localhost> (raw)
In-Reply-To: <1272461137.7750.30.camel@localhost>
On Wed, 2010-04-28 at 16:25 +0300, Artem Bityutskiy wrote:
> On Fri, 2010-04-16 at 17:41 +0200, Anatolij Gustschin wrote:
> > Signed-off-by: Anatolij Gustschin <agust@denx.de>
> > ---
> > drivers/mtd/mtdchar.c | 29 ++++++++++++++++++++++++++++-
> > 1 files changed, 28 insertions(+), 1 deletions(-)
> >
>
> Taken this to l2-mtd-2.6.git / dunno
Removed, because it breaks compilation on my x86_64:
[dedekind@sauron l2-mtd-2.6]\$ make -j8
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC [M] drivers/mtd/mtdchar.o
CHK include/linux/version.h
make[2]: `scripts/unifdef' is up to date.
Building modules, stage 2.
Kernel: arch/x86/boot/bzImage is ready (#3)
MODPOST 1635 modules
ERROR: "phys_mem_access_prot" [drivers/mtd/mtdchar.ko] undefined!
WARNING: modpost: Found 11 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
[dedekind@sauron l2-mtd-2.6]\$ git
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-04-28 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 15:41 [PATCH] mtdchar: allow mmap() on MTD RAM/ROM char devices Anatolij Gustschin
2010-04-28 13:25 ` Artem Bityutskiy
2010-04-28 13:31 ` Artem Bityutskiy [this message]
2010-04-28 16:20 ` [PATCH v2] " Anatolij Gustschin
2010-04-29 14:13 ` Anatolij Gustschin
2010-05-04 13:45 ` Artem Bityutskiy
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=1272461518.7750.31.camel@localhost \
--to=dedekind1@gmail.com \
--cc=agust@denx.de \
--cc=dwmw2@infradead.org \
--cc=dzu@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.