[clang-tidy] Fix the documentation for linuxkernel-must-use-errs.

[tmroeder]

Summary

This changes ReleaseNotes.txt to have the first sentence of the full
documentation from linuxkernel-must-use-errs.rst.

This addresses a comment from the review of rL367071 in
https://reviews.llvm.org/D59963.

[Eugene.Zelenko]

Looks OK, but please make this changes in D59963.

[Eugene.Zelenko]

Sorry, I didn't notice that D59963 was committed. In general it's not good idea to commit changes when patch was not approved.

[tmroeder]

Apologies about D59963; I should have waited longer to make sure things were resolved. My submission raced with a flip from being approved to land to not approved to land.

I'll wait longer next time to make sure comments and approvals are stable.

[tmroeder]

Sync to HEAD to prepare for commit.

clang-tools-extra/trunk/docs/ReleaseNotes.rst

 
 Improvements to clang-tidy
 --------------------------
 
 - New :doc:`linuxkernel-must-use-errs
   <clang-tidy/checks/linuxkernel-must-use-errs>` check.
 
   Checks Linux kernel code to see if it uses the results from the functions in
-  ``linux/err.h``. Also checks to see if code uses the results from functions that
-  directly return a value from one of these error functions.
-
-  This is important in the Linux kernel because ``ERR_PTR``, ``PTR_ERR``,
-  ``IS_ERR``, ``IS_ERR_OR_NULL``, ``ERR_CAST``, and ``PTR_ERR_OR_ZERO`` return
-  values must be checked, since positive pointers and negative error codes are
-  being used in the same context. These functions are marked with
-  ``__attribute__((warn_unused_result))``, but some kernel versions do not have
-  this warning enabled for clang.
+  ``linux/err.h``.
 
 - New :doc:`google-upgrade-googletest-case
   <clang-tidy/checks/google-upgrade-googletest-case>` check.
 
   Finds uses of deprecated Googletest APIs with names containing ``case`` and
   replaces them with equivalent APIs with ``suite``.
 
 

clang-tools-extra/trunk/docs/clang-tidy/checks/linuxkernel-must-use-errs.rst

 .. title:: clang-tidy - linuxkernel-must-use-errs
 
 linuxkernel-must-use-errs
 =========================
 
-Checks for cases where the kernel error functions ``ERR_PTR``,
-``PTR_ERR``, ``IS_ERR``, ``IS_ERR_OR_NULL``, ``ERR_CAST``, and
-``PTR_ERR_OR_ZERO`` are called but the results are not used. These
-functions are marked with ``__attribute__((warn_unused_result))``, but
-the compiler warning for this attribute is not always enabled.
-
-This also checks for unused values returned by functions that return
-``ERR_PTR``.
+Checks Linux kernel code to see if it uses the results from the functions in
+``linux/err.h``. Also checks to see if code uses the results from functions that
+directly return a value from one of these error functions.
+
+This is important in the Linux kernel because ``ERR_PTR``, ``PTR_ERR``,
+``IS_ERR``, ``IS_ERR_OR_NULL``, ``ERR_CAST``, and ``PTR_ERR_OR_ZERO`` return
+values must be checked, since positive pointers and negative error codes are
+being used in the same context. These functions are marked with
+``__attribute__((warn_unused_result))``, but some kernel versions do not have
+this warning enabled for clang.
 
 Examples:
 
 .. code-block:: c
 
   /* Trivial unused call to an ERR function */
   PTR_ERR_OR_ZERO(some_function_call());
 
   /* A function that returns ERR_PTR. */
   void *fn() { ERR_PTR(-EINVAL); }
 
   /* An invalid use of fn. */
   fn();