Re: [PATCH 1/9] drm: fix trivial typos

[Alex Deucher]

On Sun, Oct 18, 2015 at 11:29 AM, Geliang Tang <geliangtang@xxxxxxx> wrote:
> s/regsiter/register/
>
> Signed-off-by: Geliang Tang <geliangtang@xxxxxxx>

Applied.  thanks!

Alex

> ---
>  drivers/gpu/drm/amd/include/atombios.h          | 2 +-
>  drivers/gpu/drm/radeon/cayman_blit_shaders.c    | 2 +-
>  drivers/gpu/drm/radeon/evergreen_blit_shaders.c | 2 +-
>  drivers/gpu/drm/radeon/r600_blit_shaders.c      | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/include/atombios.h b/drivers/gpu/drm/amd/include/atombios.h
> index 44c5d4a..5526226 100644
> --- a/drivers/gpu/drm/amd/include/atombios.h
> +++ b/drivers/gpu/drm/amd/include/atombios.h
> @@ -6784,7 +6784,7 @@ typedef struct _ATOM_MC_INIT_PARAM_TABLE_V2_1
>    ULONG                         ulMCUcodeRomStartAddr;
>    ULONG                         ulMCUcodeLength;
>    USHORT                        usMcRegInitTableOffset;     // offset of ATOM_REG_INIT_SETTING array for MC core register settings.
> -  USHORT                        usReserved;                 // offset of ATOM_INIT_REG_BLOCK for MC SEQ/PHY regsiter setting
> +  USHORT                        usReserved;                 // offset of ATOM_INIT_REG_BLOCK for MC SEQ/PHY register setting
>  }ATOM_MC_INIT_PARAM_TABLE_V2_1;
>
>
> diff --git a/drivers/gpu/drm/radeon/cayman_blit_shaders.c b/drivers/gpu/drm/radeon/cayman_blit_shaders.c
> index 98d009e..9fec4d0 100644
> --- a/drivers/gpu/drm/radeon/cayman_blit_shaders.c
> +++ b/drivers/gpu/drm/radeon/cayman_blit_shaders.c
> @@ -32,7 +32,7 @@
>   * evergreen cards need to use the 3D engine to blit data which requires
>   * quite a bit of hw state setup.  Rather than pull the whole 3D driver
>   * (which normally generates the 3D state) into the DRM, we opt to use
> - * statically generated state tables.  The regsiter state and shaders
> + * statically generated state tables.  The register state and shaders
>   * were hand generated to support blitting functionality.  See the 3D
>   * driver or documentation for descriptions of the registers and
>   * shader instructions.
> diff --git a/drivers/gpu/drm/radeon/evergreen_blit_shaders.c b/drivers/gpu/drm/radeon/evergreen_blit_shaders.c
> index d433834..1a96ddb 100644
> --- a/drivers/gpu/drm/radeon/evergreen_blit_shaders.c
> +++ b/drivers/gpu/drm/radeon/evergreen_blit_shaders.c
> @@ -32,7 +32,7 @@
>   * evergreen cards need to use the 3D engine to blit data which requires
>   * quite a bit of hw state setup.  Rather than pull the whole 3D driver
>   * (which normally generates the 3D state) into the DRM, we opt to use
> - * statically generated state tables.  The regsiter state and shaders
> + * statically generated state tables.  The register state and shaders
>   * were hand generated to support blitting functionality.  See the 3D
>   * driver or documentation for descriptions of the registers and
>   * shader instructions.
> diff --git a/drivers/gpu/drm/radeon/r600_blit_shaders.c b/drivers/gpu/drm/radeon/r600_blit_shaders.c
> index 34c8b23..443cbe5 100644
> --- a/drivers/gpu/drm/radeon/r600_blit_shaders.c
> +++ b/drivers/gpu/drm/radeon/r600_blit_shaders.c
> @@ -32,7 +32,7 @@
>   * R6xx+ cards need to use the 3D engine to blit data which requires
>   * quite a bit of hw state setup.  Rather than pull the whole 3D driver
>   * (which normally generates the 3D state) into the DRM, we opt to use
> - * statically generated state tables.  The regsiter state and shaders
> + * statically generated state tables.  The register state and shaders
>   * were hand generated to support blitting functionality.  See the 3D
>   * driver or documentation for descriptions of the registers and
>   * shader instructions.
> --
> 2.5.0
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/