From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Tso <tytso@MIT•EDU>
Cc: linux-next@vger•kernel.org, Mingming Cao <cmm@us•ibm.com>,
Jan Kara <jack@suse•cz>
Subject: linux-next: manual merge of the ext4 tree with the tree
Date: Wed, 25 Feb 2009 12:52:54 +1100 [thread overview]
Message-ID: <20090225125254.6e94f404.sfr@canb.auug.org.au> (raw)
Hi Ted,
Today's linux-next merge of the ext4 tree got a conflict in
fs/ext4/ext4.h between commit 7c989bb2f1b18268968ce44c603f18a9854b1b85
("ext4: quota reservation for delayed allocation") from the quota tree
and commit eafffefbb8cc3db4acebb75014091b473c60007d ("ext4: add
EXT4_IOC_ALLOC_DA_BLKS ioctl") from the ext4 tree.
Just overlapping additions. I fixed it up (see below) and can carry the
fix as necessary.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
diff --cc fs/ext4/ext4.h
index 6083bb3,09626d3..0000000
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@@ -1099,7 -1097,7 +1098,8 @@@ extern int ext4_chunk_trans_blocks(stru
extern int ext4_block_truncate_page(handle_t *handle,
struct address_space *mapping, loff_t from);
extern int ext4_page_mkwrite(struct vm_area_struct *vma, struct page *page);
+extern qsize_t ext4_get_reserved_space(struct inode *inode);
+ extern int ext4_alloc_da_blocks(struct inode *inode);
/* ioctl.c */
extern long ext4_ioctl(struct file *, unsigned int, unsigned long);
next reply other threads:[~2009-02-25 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:52 Stephen Rothwell [this message]
2009-02-25 9:43 ` linux-next: manual merge of the ext4 tree with the tree Jan Kara
2009-02-26 6:03 ` Theodore Tso
2009-02-26 8:36 ` Stephen Rothwell
2009-02-26 14:08 ` Theodore Tso
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 2:03 Stephen Rothwell
2009-03-03 19:09 ` Jan Kara
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=20090225125254.6e94f404.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cmm@us$(echo .)ibm.com \
--cc=jack@suse$(echo .)cz \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tytso@MIT$(echo .)EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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