summaryrefslogtreecommitdiffstats
path: root/fs/openpromfs
diff options
context:
space:
mode:
authorLinus Torvalds2012-05-21 17:41:38 +0200
committerLinus Torvalds2012-05-21 17:41:38 +0200
commit8c12fec90c54cfabdd57b2726a1defbc07c19a55 (patch)
treed9a42d2508ec8ce651a978bd5bbbcf3205a77e1d /fs/openpromfs
parentMerge branch 'vm-cleanups' (unmap_vma() interface cleanup) (diff)
parentvfs: don't force a big memset of stat data just to clear padding fields (diff)
downloadkernel-qcow2-linux-8c12fec90c54cfabdd57b2726a1defbc07c19a55.tar.gz
kernel-qcow2-linux-8c12fec90c54cfabdd57b2726a1defbc07c19a55.tar.xz
kernel-qcow2-linux-8c12fec90c54cfabdd57b2726a1defbc07c19a55.zip
Merge branch 'stat-cleanups' (clean up copying of stat info to user space)
This makes cp_new_stat() a bit more readable, and avoids having to memset() the whole structure just to fill in a couple of padding fields. This is another result of me looking at code generation of functions that show up high on certain kernel profiles, and just going "Oh, let's just clean that up". Architectures that don't supply the #define to fill just the padding fields will still fall back to memset(). * stat-cleanups: vfs: don't force a big memset of stat data just to clear padding fields vfs: de-crapify "cp_new_stat()" function
Diffstat (limited to 'fs/openpromfs')
0 files changed, 0 insertions, 0 deletions