On Mon, 10 May 2021, Mauro Carvalho Chehab mchehab+huawei@kernel.org wrote:
While UTF-8 characters can be used at the Linux documentation, the best is to use them only when ASCII doesn't offer a good replacement. So, replace the occurences of the following UTF-8 characters:
- U+2019 ('’'): RIGHT SINGLE QUOTATION MARK
Signed-off-by: Mauro Carvalho Chehab mchehab+huawei@kernel.org
Acked-by: Jani Nikula jani.nikula@intel.com
Documentation/gpu/i915.rst | 2 +- Documentation/gpu/komeda-kms.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst index 486c720f3890..2cbf54460b48 100644 --- a/Documentation/gpu/i915.rst +++ b/Documentation/gpu/i915.rst @@ -361,7 +361,7 @@ Locking Guidelines real bad.
#. Do not nest different lru/memory manager locks within each other.
- Take them in turn to update memory allocations, relying on the object’s
- Take them in turn to update memory allocations, relying on the object's dma_resv ww_mutex to serialize against other operations.
#. The suggestion for lru/memory managers locks is that they are small diff --git a/Documentation/gpu/komeda-kms.rst b/Documentation/gpu/komeda-kms.rst index eb693c857e2d..c2067678e92c 100644 --- a/Documentation/gpu/komeda-kms.rst +++ b/Documentation/gpu/komeda-kms.rst @@ -324,7 +324,7 @@ the control-abilites of device.
We have &komeda_dev, &komeda_pipeline, &komeda_component. Now fill devices with pipelines. Since komeda is not for D71 only but also intended for later products, -of course we’d better share as much as possible between different products. To +of course we'd better share as much as possible between different products. To achieve this, split the komeda device into two layers: CORE and CHIP.
- CORE: for common features and capabilities handling.