From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Felipe Balbi <balbi@ti.com>
Cc: Dongsheng Song <dongsheng.song@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Linux 3.8.3
Date: Sun, 17 Mar 2013 19:57:10 +0000 [thread overview]
Message-ID: <20130317195709.GC4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130317193321.GA15102@arwen.pp.htv.fi>
On Sun, Mar 17, 2013 at 09:33:21PM +0200, Felipe Balbi wrote:
> Hi,
>
> On Sun, Mar 17, 2013 at 10:00:08PM +0800, Dongsheng Song wrote:
> > “make ARCH=arm menuconfig” no complains, but "make ARCH=arm
> > CROSS_COMPILE=arm-linux-gnueabihf-" failed:
> >
> > $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> > CHK include/generated/uapi/linux/version.h
> > CHK include/generated/utsrelease.h
> > make[1]: `include/generated/mach-types.h' is up to date.
> > CALL scripts/checksyscalls.sh
> > CHK include/generated/compile.h
> > CHK kernel/config_data.h
> > Kernel: arch/arm/boot/Image is ready
> > Kernel: arch/arm/boot/zImage is ready
> > Building modules, stage 2.
> > MODPOST 1904 modules
> > ERROR: "flush_tlb_kernel_range" [drivers/staging/zsmalloc/zsmalloc.ko]
> > undefined!
> > make[1]: *** [__modpost] Error 1
> > make: *** [modules] Error 2
> >
> > Please find the attachment with .config.gz file.
>
> linux-arm-kernel might have more information about this.
Sigh.
At times, I really don't know why I bother wasting my time commenting on
patches if they just go and agree with them, and promptly ignore them.
I pointed out what this should be:
http://marc.info/?l=linux-kernel&m=135972750522902&w=2
And it was agreed:
http://marc.info/?l=linux-kernel&m=135993546317541&w=2
But for some reason the wrong patch got merged:
http://marc.info/?l=git-commits-head&m=136147889001219&w=2
Maybe because it was "simpler" ? Don't know. But... well, we now know
what the outcome of it was. Let's try a different technique. I'm going
to say nothing of any real help and hopefully it will get fixed properly.
Maybe that'll work.
next prev parent reply other threads:[~2013-03-17 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 18:47 Greg KH
2013-03-14 18:47 ` Greg KH
2013-03-17 14:00 ` Dongsheng Song
2013-03-17 14:05 ` Greg KH
2013-03-17 14:31 ` Dongsheng Song
2013-03-17 19:33 ` Felipe Balbi
2013-03-17 19:57 ` Russell King - ARM Linux [this message]
2013-03-17 20:10 ` Bjørn Mork
2013-03-18 2:51 ` Greg KH
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=20130317195709.GC4977@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=balbi@ti.com \
--cc=dongsheng.song@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®