All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/10] drm/i915/dmc: use kernel types
Date: Thu, 23 May 2019 10:34:39 -0700	[thread overview]
Message-ID: <20190523173439.GP4441@intel.com> (raw)
In-Reply-To: <20190523082420.10352-1-lucas.demarchi@intel.com>

On Thu, May 23, 2019 at 01:24:11AM -0700, Lucas De Marchi wrote:
> Change all fields in intel_package_header and intel_dmc_header whose
> meaning are 1-byte numbers to use u8.
> 
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/i915/intel_csr.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
> index 4527b9662330..b05e7a6aebc7 100644
> --- a/drivers/gpu/drm/i915/intel_csr.c
> +++ b/drivers/gpu/drm/i915/intel_csr.c
> @@ -130,12 +130,12 @@ struct intel_fw_info {
>  
>  struct intel_package_header {
>  	/* DMC container header length in dwords */
> -	unsigned char header_len;
> +	u8 header_len;
>  
>  	/* always value would be 0x01 */
> -	unsigned char header_ver;
> +	u8 header_ver;
>  
> -	unsigned char reserved[10];
> +	u8 reserved[10];
>  
>  	/* Number of valid entries in the FWInfo array below */
>  	u32 num_entries;
> @@ -148,10 +148,10 @@ struct intel_dmc_header {
>  	u32 signature;
>  
>  	/* DMC binary header length */
> -	unsigned char header_len;
> +	u8 header_len;
>  
>  	/* 0x01 */
> -	unsigned char header_ver;
> +	u8 header_ver;
>  
>  	/* Reserved */
>  	u16 dmcc_ver;
> -- 
> 2.21.0
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-05-23 17:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  8:24 [PATCH 01/10] drm/i915/dmc: use kernel types Lucas De Marchi
2019-05-23  8:24 ` [PATCH 02/10] drm/i915/dmc: extract fw_info and table walk from intel_package_header Lucas De Marchi
2019-05-23 17:36   ` Rodrigo Vivi
2019-05-23 17:45   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 03/10] drm/i915/dmc: add support for package_header with version 2 Lucas De Marchi
2019-05-23 17:43   ` Rodrigo Vivi
2019-05-23 17:55     ` Lucas De Marchi
2019-05-23 17:49   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 04/10] drm/i915/dmc: extract function to parse css header Lucas De Marchi
2019-05-23 17:45   ` Rodrigo Vivi
2019-05-23 17:51   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 05/10] drm/i915/dmc: extract function to parse package_header Lucas De Marchi
2019-05-23 18:03   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 06/10] drm/i915/dmc: extract function to parse dmc_header Lucas De Marchi
2019-05-23 18:22   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 07/10] drm/i915/dmc: add support to load dmc_header version 3 Lucas De Marchi
2019-05-23 18:26   ` Srivatsa, Anusha
2019-05-23 18:57   ` Rodrigo Vivi
2019-05-23 19:25     ` Lucas De Marchi
2019-05-23 23:27       ` Rodrigo Vivi
2019-05-23  8:24 ` [PATCH 08/10] drm/i915/dmc: remove redundant return in parse_csr_fw() Lucas De Marchi
2019-05-23 18:28   ` Srivatsa, Anusha
2019-05-23  8:24 ` [PATCH 09/10] drm/i915/dmc: protect against reading random memory Lucas De Marchi
2019-05-23 18:58   ` Rodrigo Vivi
2019-05-23 19:41     ` Lucas De Marchi
2019-05-23  8:24 ` [PATCH 10/10] drm/i915/dmc: protect against loading wrong firmware Lucas De Marchi
2019-05-23 19:00   ` Rodrigo Vivi
2019-05-23 16:13 ` ✓ Fi.CI.BAT: success for series starting with [01/10] drm/i915/dmc: use kernel types Patchwork
2019-05-23 17:32 ` [PATCH 01/10] " Srivatsa, Anusha
2019-05-23 17:34 ` Rodrigo Vivi [this message]
2019-05-24 23:56 ` ✓ Fi.CI.IGT: success for series starting with [01/10] " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190523173439.GP4441@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.