From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] drm/i915: move towards kernel types
Date: Wed, 13 Jun 2018 09:55:38 +0300 [thread overview]
Message-ID: <87sh5r18gl.fsf@intel.com> (raw)
In-Reply-To: <CAKi4VA++Pr53u8p7w2NU=AFzBTKJKvV1c1Md_rX4z1XGRcX+yA@mail.gmail.com>
On Tue, 12 Jun 2018, Lucas De Marchi <lucas.de.marchi@gmail.com> wrote:
> On Tue, Jun 12, 2018 at 3:15 AM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> On Tue, 12 Jun 2018, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
>> > On 12/06/2018 10:19, Jani Nikula wrote:
>> >> Semi-RFC. Do we want to do this? Here's a batch of conversions that shouldn't
>> >> conflict much with in-flight patches.
>> >>
>> >> The trouble with mixed use is that it's inconsistent, and any remaining C99
>> >> types will encourage their use. We could at least do the low hanging fruit?
>> >
>> > Ack from me. Doesn't seem so big to cause much pain.
>> >
>> > When you say low-hanging fruit, that implies you only dealt with a
>> > particular class of occurrences?
>>
>> I meant the files which don't have massive amounts of C99 types and
>> aren't under active development right now. I just wanted to avoid
>> trouble for starters. ;)
>
> If using kernel types is where we want to go (which I agree with),
> maybe it would be better to have a single conversion rather than
> several small ones as we are doing with dev_priv -> i915? This allows
> in-flight-but-not-yet-sent patches to easily keep up with the changes
> rather than conflicting every other rebase.
I'm thinking we can do a lot of changes without conflicting anything or
very little. At least for starters before the sudden ripping off the
band-aid.
BR,
Jani.
>
> Lucas De Marchi
>
>>
>> > Also going forward we have to make sure we will be able to stop them
>> > creeping back in. Is checkpatch perhaps covering this? Or we could put
>> > something in dim?
>>
>> We can stop ignoring PREFER_KERNEL_TYPES in checkpatch (the ignores are
>> in dim). We don't even have to change everything for that, we just need
>> to change enough to make the S/N better. People tend to use the types
>> near the places they change.
>>
>> BR,
>> Jani.
>>
>>
>> >
>> > Regards,
>> >
>> > Tvrtko
>> >
>> >> $ git grep "uint\(8\|16\|32\|64\)_t" -- drivers/gpu/drm/i915/ | sed 's/:.*//' | sort | uniq -c | sort -n
>> >>
>> >> BR,
>> >> Jani.
>> >>
>> >>
>> >> Jani Nikula (7):
>> >> drm/i915/vbt: switch to kernel unsigned int types
>> >> drm/i915/hdmi: switch to kernel unsigned int types
>> >> drm/i915/uncore: switch to kernel unsigned int types
>> >> drm/i915/dvo: switch to kernel unsigned int types
>> >> drm/i915/backlight: switch to kernel unsigned int types
>> >> drm/i915/audio: switch to kernel unsigned int types
>> >> drm/i915/lspcon: switch to kernel unsigned int types
>> >>
>> >> drivers/gpu/drm/i915/dvo_ch7017.c | 20 ++++++------
>> >> drivers/gpu/drm/i915/dvo_ch7xxx.c | 22 +++++++-------
>> >> drivers/gpu/drm/i915/dvo_ivch.c | 26 ++++++++--------
>> >> drivers/gpu/drm/i915/dvo_ns2501.c | 44 +++++++++++++--------------
>> >> drivers/gpu/drm/i915/dvo_sil164.c | 10 +++---
>> >> drivers/gpu/drm/i915/dvo_tfp410.c | 16 +++++-----
>> >> drivers/gpu/drm/i915/intel_audio.c | 36 +++++++++++-----------
>> >> drivers/gpu/drm/i915/intel_bios.c | 4 +--
>> >> drivers/gpu/drm/i915/intel_dp_aux_backlight.c | 12 ++++----
>> >> drivers/gpu/drm/i915/intel_dvo.c | 2 +-
>> >> drivers/gpu/drm/i915/intel_hdmi.c | 14 ++++-----
>> >> drivers/gpu/drm/i915/intel_lspcon.c | 2 +-
>> >> drivers/gpu/drm/i915/intel_panel.c | 8 ++---
>> >> drivers/gpu/drm/i915/intel_uncore.h | 22 +++++++-------
>> >> drivers/gpu/drm/i915/intel_vbt_defs.h | 2 +-
>> >> 15 files changed, 120 insertions(+), 120 deletions(-)
>> >>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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:[~2018-06-13 6:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 9:19 [PATCH 0/7] drm/i915: move towards kernel types Jani Nikula
2018-06-12 9:19 ` [PATCH 1/7] drm/i915/vbt: switch to kernel unsigned int types Jani Nikula
2018-06-12 9:19 ` [PATCH 2/7] drm/i915/hdmi: " Jani Nikula
2018-06-12 9:19 ` [PATCH 3/7] drm/i915/uncore: " Jani Nikula
2018-06-12 9:19 ` [PATCH 4/7] drm/i915/dvo: " Jani Nikula
2018-06-12 9:56 ` [PATCH v2 " Jani Nikula
2018-06-12 9:19 ` [PATCH 5/7] drm/i915/backlight: " Jani Nikula
2018-06-12 9:19 ` [PATCH 6/7] drm/i915/audio: " Jani Nikula
2018-06-12 13:13 ` Ville Syrjälä
2018-06-12 9:19 ` [PATCH 7/7] drm/i915/lspcon: " Jani Nikula
2018-06-12 9:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: move towards kernel types Patchwork
2018-06-12 9:35 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-06-12 9:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-12 9:59 ` [PATCH 0/7] " Tvrtko Ursulin
2018-06-12 10:09 ` Jani Nikula
2018-06-12 23:28 ` Lucas De Marchi
2018-06-13 6:55 ` Jani Nikula [this message]
2018-06-14 18:54 ` Rodrigo Vivi
2018-06-15 9:08 ` Jani Nikula
2018-06-18 8:39 ` Joonas Lahtinen
2018-06-18 11:53 ` Jani Nikula
2018-06-19 6:55 ` Lucas De Marchi
2018-06-12 10:14 ` ✗ Fi.CI.SPARSE: warning for drm/i915: move towards kernel types (rev2) Patchwork
2018-06-12 10:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-12 12:23 ` ✓ Fi.CI.IGT: " Patchwork
2018-06-12 13:17 ` [PATCH 0/7] drm/i915: move towards kernel types Ville Syrjälä
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=87sh5r18gl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.de.marchi@gmail.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