public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Hawco <ghawco@cox.net>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Problem compiling 2.6.260rc6 with updated ext4-patch-queue
Date: Tue, 24 Jun 2008 10:26:59	[thread overview]
Message-ID: <3.0.6.32.20080624102659.02429f60@pop.west.cox.net> (raw)

Recently pulled and updated my ext4-patch-queue. Tried to compile the
2.6.26-rc6 after it patched cleanly. During make received the following error:

fs/ext4/inode.c: In function 'ext4_journal_dirty_data':
fs/ext4/inode.c:1297: error:  implicit declaration of function
'jbd2_journal_dirty_data'
fs/ext4/inode.c: In function 'ext4_da_writepages':
fs/ext4/inode.c:1759: error:  implicit declaration of function
'ext4_jbd2_file_inode'
make[2]: *** [fs/ext4/inode.o]  Error 1
make[1]: *** [fs/ext4] Error 2
make:  *** [fs] Error 2

Previously, as of the Add ext4-delalloc-bmap-support.patch by Mingming Cao
three days ago, the 2.6.26-rc6 kernel compiled cleanly, so I would guess
it's something in the last seven patches (listed from newest to oldest):

1. Fold ext4-Use-new-framework-for-data-ordered-mode-in-JBD.patch
2. Fix compile error in ext4_use_atomic-function-to-set-bh_stat-fix.patch
3. Added ext4_use_atomic-function-to-set-bh_stat-fix.patch
4. Update changelog for jbd2-Implement-data-ordered-mode-handling-via-
inode.patch
5. Fold ext4-delalloc-bmap-support.patch to delalloc writeback mode patch
6. Fold delalloc-ext4-reservation-for-nonextent-files.patch to delalloc
ENOSPC error handling patch, move it before reverse locking changes
7. Add delalloc-ext4-reservation-for-nonextent-files.patch

Gary



             reply	other threads:[~2008-06-24 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 10:26 Gary Hawco [this message]
2008-06-24 22:18 ` Problem compiling 2.6.260rc6 with updated ext4-patch-queue Theodore Tso
2008-06-24 22:34   ` Mingming

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=3.0.6.32.20080624102659.02429f60@pop.west.cox.net \
    --to=ghawco@cox.net \
    --cc=linux-ext4@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