The patch titled
ecryptfs: fix printk format warning
has been removed from the -mm tree. Its filename was
ecryptfs-remove-header_extent_size-fix.patch
This patch was dropped because it was folded into ecryptfs-remove-header_extent_size.patch
------------------------------------------------------
Subject: ecryptfs: fix printk format warning
From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Fix printk format warning:
fs/ecryptfs/crypto.c:1443: warning: format '%d' expects type 'int', but argument 2 has type 'size_t'
Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Cc: Michael Halcrow <mhalcrow@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ecryptfs/crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/ecryptfs/crypto.c~ecryptfs-remove-header_extent_size-fix fs/ecryptfs/crypto.c
--- a/fs/ecryptfs/crypto.c~ecryptfs-remove-header_extent_size-fix
+++ a/fs/ecryptfs/crypto.c
@@ -1542,7 +1542,7 @@ static int parse_header_metadata(struct
* crypt_stat->num_header_extents_at_front)
< ECRYPTFS_MINIMUM_HEADER_EXTENT_SIZE)) {
rc = -EINVAL;
- printk(KERN_WARNING "Invalid number of header extents: [%d]\n",
+ printk(KERN_WARNING "Invalid number of header extents: [%zd]\n",
crypt_stat->num_header_extents_at_front);
}
return rc;
_
Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are
origin.patch
mm-use-pagevec-to-rotate-reclaimable-page.patch
ecryptfs-remove-header_extent_size.patch
ecryptfs-remove-header_extent_size-fix.patch
video-gfx-fix-menu-ordering.patch
video-gfx-merge-kconfig-menus.patch
kernel-doc-fix-doc-blocks-and-html.patch
express-relocatability-of-kernel-on-x86_64-in.patch
remap_file_pages-kernel-doc-corrections.patch
hook-up-group-scheduler-with-control-groups.patch
hook-up-group-scheduler-with-control-groups-fix.patch
combine-instrumentation-menus-in-kernel-kconfiginstrumentation.patch
add-samples-subdir.patch
profile-likely-unlikely-macros.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
