From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/i915: make intel_sdvo_regs.h self-contained
Date: Thu, 13 Jun 2019 12:36:20 +0300 [thread overview]
Message-ID: <87v9x9x1wr.fsf@intel.com> (raw)
In-Reply-To: <156041738573.27443.11336619597847360845@skylake-alporthouse-com>
On Thu, 13 Jun 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2019-06-13 09:44:14)
>> Ensure intel_sdvo_regs.h is self-contained and remains that way.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/Makefile.header-test | 1 +
>> drivers/gpu/drm/i915/intel_sdvo_regs.h | 7 +++++++
>> 2 files changed, 8 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/Makefile.header-test b/drivers/gpu/drm/i915/Makefile.header-test
>> index 6ef3b647ac65..c04297ce57b4 100644
>> --- a/drivers/gpu/drm/i915/Makefile.header-test
>> +++ b/drivers/gpu/drm/i915/Makefile.header-test
>> @@ -56,6 +56,7 @@ header_test := \
>> intel_quirks.h \
>> intel_runtime_pm.h \
>> intel_sdvo.h \
>> + intel_sdvo_regs.h \
>> intel_sideband.h \
>> intel_sprite.h \
>> intel_tv.h \
>> diff --git a/drivers/gpu/drm/i915/intel_sdvo_regs.h b/drivers/gpu/drm/i915/intel_sdvo_regs.h
>> index e9ba3b047f93..af02c0d21d6b 100644
>> --- a/drivers/gpu/drm/i915/intel_sdvo_regs.h
>> +++ b/drivers/gpu/drm/i915/intel_sdvo_regs.h
>> @@ -24,6 +24,11 @@
>> * Eric Anholt <eric@anholt.net>
>> */
>>
>> +#ifndef __INTEL_SDVO_REGS_H__
>> +#define __INTEL_SDVO_REGS_H__
>> +
>
> #include <linux/compiler.h> or compiler_attributes.h for __packed
>
> Looks like random inclusion otherwise.
>
>> +#include <linux/types.h>
Huh, no errors about __packed that I could see, what am I missing?
<linux/types.h> is for kernel unsigned types.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-13 9:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 8:44 [PATCH v2 1/3] drm/i915: make intel_sdvo_regs.h self-contained Jani Nikula
2019-06-13 8:44 ` [PATCH v2 2/3] drm/i915: move modesetting output/encoder code under display/ Jani Nikula
2019-06-13 8:44 ` [PATCH v2 3/3] drm/i915: move modesetting core " Jani Nikula
2019-06-13 14:12 ` Maarten Lankhorst
2019-06-17 8:58 ` Jani Nikula
2019-06-13 9:16 ` [PATCH v2 1/3] drm/i915: make intel_sdvo_regs.h self-contained Chris Wilson
2019-06-13 9:36 ` Jani Nikula [this message]
2019-06-13 9:38 ` Chris Wilson
2019-06-13 9:45 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] " Patchwork
2019-06-13 9:47 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-13 10:08 ` [PATCH v2] " Jani Nikula
2019-06-13 10:12 ` Chris Wilson
2019-06-13 10:15 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/3] " Patchwork
2019-06-13 10:40 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2] drm/i915: make intel_sdvo_regs.h self-contained (rev2) Patchwork
2019-06-13 10:41 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-13 12:07 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-14 21:20 ` ✓ 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=87v9x9x1wr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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