Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/sdvo: prefer __packed over __attribute__((packed))
Date: Thu, 17 Mar 2022 19:38:29 +0200	[thread overview]
Message-ID: <YjNyFdyA3vQAT4i0@intel.com> (raw)
In-Reply-To: <20220317173355.336835-1-jani.nikula@intel.com>

On Thu, Mar 17, 2022 at 07:33:55PM +0200, Jani Nikula wrote:
> The kernel preference is to use the __packed macro instead of the direct
> __attribute__.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_sdvo.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_sdvo.c b/drivers/gpu/drm/i915/display/intel_sdvo.c
> index 158e750e5b4d..328a8f20c63b 100644
> --- a/drivers/gpu/drm/i915/display/intel_sdvo.c
> +++ b/drivers/gpu/drm/i915/display/intel_sdvo.c
> @@ -283,7 +283,7 @@ static bool intel_sdvo_read_byte(struct intel_sdvo *intel_sdvo, u8 addr, u8 *ch)
>  static const struct {
>  	u8 cmd;
>  	const char *name;
> -} __attribute__ ((packed)) sdvo_cmd_names[] = {
> +} __packed sdvo_cmd_names[] = {
>  	SDVO_CMD_NAME_ENTRY(RESET),
>  	SDVO_CMD_NAME_ENTRY(GET_DEVICE_CAPS),
>  	SDVO_CMD_NAME_ENTRY(GET_FIRMWARE_REV),
> -- 
> 2.30.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-03-17 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 17:33 [Intel-gfx] [PATCH] drm/i915/sdvo: prefer __packed over __attribute__((packed)) Jani Nikula
2022-03-17 17:38 ` Ville Syrjälä [this message]
2022-03-21 13:42   ` Jani Nikula
2022-03-17 19:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-17 21:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=YjNyFdyA3vQAT4i0@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox