linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitri Vorobiev" <dmitri.vorobiev@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Martin Michlmayr" <tbm@cyrius.com>,
	linux-mips@linux-mips.org, linux-ext4@vger.kernel.org,
	ralf@linux-mips.org
Subject: Re: ext4dev build failure on mips: "empty_zero_page" undefined
Date: Mon, 12 May 2008 18:46:21 +0400	[thread overview]
Message-ID: <90edad820805120746l61e67362vbd177d63e8b05dc8@mail.gmail.com> (raw)
In-Reply-To: <20080512143426.GB7029@mit.edu>

2008/5/12 Theodore Tso <tytso@mit.edu>:
> On Mon, May 12, 2008 at 05:54:24PM +0400, Dmitri Vorobiev wrote:
>  >
>  > Yep. The export is missing. Attached patch was build-tested for a
>  > Malta config with ext4 enabled as a module.
>
>  Thanks, Dmitri!
>
>  What is the Linux-mips' team preference for feeding this patch to
>  Linus?  This technically isn't a regression, since it was broken in
>  2.6.25, but it would be nice to get this to Linus sooner rather than
>  later.  Should I push it with a batch of ext4 fixes, or do you want to
>  push it via the mips tree?  (Davem asked me to push the sparc export
>  via ext4, while the ppc arch, it went via the ppc tree.  So whichever
>  is your preference; I'm easy.  :-)
>
>                                             - Ted

Hi Ted,

Normally I push my patches via the mips tree, and now I'm Cc:ing Ralf for that.

Hopefully Ralf will react quickly. :)

Dmitri

  reply	other threads:[~2008-05-12 14:46 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 [this message]
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
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=90edad820805120746l61e67362vbd177d63e8b05dc8@mail.gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tbm@cyrius.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).