aboutsummaryrefslogtreecommitdiff
path: root/migration/ram.c
diff options
context:
space:
mode:
authorJason J. Herne <jjherne@linux.vnet.ibm.com>2015-12-11 13:30:42 -0500
committerMarkus Armbruster <armbru@redhat.com>2016-01-13 15:16:19 +0100
commit5d596c245d675000ddee69e87616d537ef273be5 (patch)
tree78a0fb9d7e16fcdb18ef22de85fba3333a99496c /migration/ram.c
parent533fdaedeb7f7ae90866312f57249ebbb7e3c97f (diff)
downloadqemu-5d596c245d675000ddee69e87616d537ef273be5.zip
qemu-5d596c245d675000ddee69e87616d537ef273be5.tar.gz
qemu-5d596c245d675000ddee69e87616d537ef273be5.tar.bz2
checkpatch: Detect newlines in error_report and other error functions
We don't want newlines embedded in error messages. This seems to be a common problem with new code so let's try to catch it with checkpatch. This will not catch cases where newlines are inserted into the middle of an existing multi-line statement. But those cases should be rare. Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com> Message-Id: <1449858642-24267-1-git-send-email-jjherne@linux.vnet.ibm.com> [Rephrased "Error function text" to "Error messages", dropped error_vprintf, error_printf, error_printf from $qemu_error_funcs, because they may legitimately print newlines] Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'migration/ram.c')
0 files changed, 0 insertions, 0 deletions