From: Waldemar Brodkorb <wbx@openadk.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Waldemar Brodkorb <wbx@openadk.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: m68k compile issue with 4.0.5
Date: Wed, 17 Jun 2015 07:28:23 +0200 [thread overview]
Message-ID: <20150617052823.GE21686@waldemar-brodkorb.de> (raw)
In-Reply-To: <CAMuHMdXKQRN0sDjYST8f00uHdibtgQsFjFijnaMniJMquboihw@mail.gmail.com>
Hi Geert,
Geert Uytterhoeven wrote,
> Hi Waldemar,
>
> On Mon, Jun 15, 2015 at 10:23 PM, Waldemar Brodkorb <wbx@openadk.org> wrote:
> > I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
> > Any idea what change breaks the compile?
>
> I tried a few m68knommu defconfigs, but can't reproduce it.
>
> Is this a plain v4.0.5? I can't find the offending call to vma_fput().
> "git grep vma_fput" tells me there's no "vma_fput" in the kernel sources?
You are totally right. It is not plain vanilla, I am really sorry
about this ugly bug report. I normally use an option to disable any
external kernel patches, before reporting. I missed it this time.
I have experimented with aufs4 kernel patches lately.
You are allowed to kick my ass ;)
best regards
Waldemar
prev parent reply other threads:[~2015-06-17 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 20:23 m68k compile issue with 4.0.5 Waldemar Brodkorb
2015-06-16 6:24 ` Geert Uytterhoeven
2015-06-16 7:02 ` [uClinux-dev] " Greg Ungerer
2015-06-17 5:42 ` Waldemar Brodkorb
2015-06-17 6:06 ` Greg Ungerer
2015-06-18 14:13 ` Greg Ungerer
2015-06-17 5:28 ` Waldemar Brodkorb [this message]
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=20150617052823.GE21686@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@waldemar-brodkorb.de \
--cc=uclinux-dev@uclinux.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.