MSM: Remove @problem.severity tags with no effect

Author: jbj

ql_demos/cpp/Qualcomm-MSM-copy_from_user/00_copy_from_user.ql

@@ -1,7 +1,6 @@
 /**
  * @name Calls to copy_from_user
  * @description Find all calls to copy_from_user.
- * @problem.severity warning
  */
 
 import cpp

ql_demos/cpp/Qualcomm-MSM-copy_from_user/01_copy_from_user_annotated.ql

@@ -2,7 +2,6 @@
  * @name Annotate with types and bounds
  * @description Find all calls to copy_from_user and annotates them with their
  *              type and inferred size bounds.
- * @problem.severity warning
  */
 
 import cpp

ql_demos/cpp/Qualcomm-MSM-copy_from_user/02_filter_with_upperbound.ql

@@ -3,7 +3,6 @@
  * @description This query excludes results that are safe because the upper
  *              bound of the size argument is less than or equal to the size of
  *              the destination variable.
- * @problem.severity warning
  */
 
 import cpp

ql_demos/cpp/Qualcomm-MSM-copy_from_user/03_filter_with_upperbound.ql

@@ -3,7 +3,6 @@
  * @description This query excludes results that are safe because the upper
  *              bound of the size argument is less than or equal to the size of
  *              the destination variable or array.
- * @problem.severity warning
  */
 
 import cpp

ql_demos/cpp/Qualcomm-MSM-copy_from_user/04_safe_malloc.ql

@@ -2,7 +2,6 @@
  * @name kzalloc only
  * @description If the copy_from_user is preceded by a kzalloc of the correct
  *              size, then it is safe. To demonstrate, find only those results.
- * @problem.severity warning
  */
 
 import cpp

ql_demos/cpp/Qualcomm-MSM-copy_from_user/05_filter_with_upperbound_and_safe_malloc.ql

@@ -5,7 +5,6 @@
  *              the destination variable or array. It also excludes results
  *              that are safe because the right amount of memory was allocated
  *              with kzalloc.
- * @problem.severity warning
  */
 
 import cpp