From: Theodore Tso <tytso@mit.edu>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: Martin Michlmayr <tbm@cyrius.com>,
linux-mips@linux-mips.org, linux-ext4@vger.kernel.org
Subject: Re: ext4dev build failure on mips: "empty_zero_page" undefined
Date: Mon, 12 May 2008 13:35:38 -0400 [thread overview]
Message-ID: <20080512173537.GG7029@mit.edu> (raw)
In-Reply-To: <90edad820805120814l7ee3f5d3h7f9939854bccf0@mail.gmail.com>
On Mon, May 12, 2008 at 07:14:23PM +0400, Dmitri Vorobiev wrote:
>
> It was April 29th 2008 when commit
> 093a088b76352e0a6fdca84eb78b3aa65fbe6dd1 where the ext4_ext_zeroout()
> routine was introduced (it is this routine that makes use of the
> ZERO_PAGE macro expanding to an expression that contains a reference
> to the empty_zero_page global symbol). After this commit, the patches
> similar to the one found in this thread were made for several
> architectures. Apparently, MIPS has been overlooked.
>
Yeah, I guess no one is currently doing test builds of linux-next on
the mips architecture. It's likely Stephen Rothwell doesn't have
access to one.
(The patch itself has been around for a while, both in the -mm tree,
the ext4 patches, and in Linux-next.)
- Ted
next prev parent reply other threads:[~2008-05-12 17:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 13:06 ext4dev build failure on mips: "empty_zero_page" undefined Martin Michlmayr
2008-05-12 13:54 ` Dmitri Vorobiev
2008-05-12 14:34 ` Theodore Tso
2008-05-12 14:46 ` Dmitri Vorobiev
2008-05-13 4:50 ` Ralf Baechle
2008-05-13 5:12 ` Ralf Baechle
2008-05-15 13:39 ` Theodore Tso
2008-05-28 7:06 ` Martin Michlmayr
2008-06-05 11:11 ` Martin Michlmayr
2008-06-05 11:22 ` Dmitri Vorobiev
2008-06-05 18:38 ` Theodore Tso
2008-06-05 21:34 ` Vorobiev Dmitri
2008-06-05 21:51 ` Thiemo Seufer
2008-06-06 6:57 ` Dmitri Vorobiev
2008-06-06 13:15 ` Theodore Tso
2008-05-12 14:58 ` Martin Michlmayr
2008-05-12 15:14 ` Dmitri Vorobiev
2008-05-12 17:35 ` Theodore Tso [this message]
2008-05-12 19:37 ` Dmitri Vorobiev
2008-05-13 0:55 ` Stephen Rothwell
2008-05-13 1:42 ` Stephen Rothwell
2008-05-13 4:23 ` Ralf Baechle
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=20080512173537.GG7029@mit.edu \
--to=tytso@mit.edu \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.com \
/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.