From: Jani Nikula <jani.nikula@intel.com>
To: Ander Conselvan De Oliveira <conselvan2@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-intel-next-fixes
Date: Mon, 22 Jun 2015 11:12:04 +0300 [thread overview]
Message-ID: <878ubc2mcr.fsf@intel.com> (raw)
In-Reply-To: <1434959949.3591.3.camel@gmail.com>
On Mon, 22 Jun 2015, Ander Conselvan De Oliveira <conselvan2@gmail.com> wrote:
> There is
>
> commit bd4b4827acdc00bf9e71f939d160102021d10d4f
> Author: Ander Conselvan de Oliveira
> <ander.conselvan.de.oliveira@intel.com>
> Date: Fri May 29 14:28:09 2015 +0300
>
> drm/i915: Silence compiler warning
>
> in -nightly to fix that same issue. I didn't realize this was also
> needed in -next-fixes.
Dave, sorry, I didn't see the warning, gcc 4.9.2 here.
Do you want another pull request with Ander's fix on top?
BR,
Jani.
>
>
> Ander
>
> On Fri, 2015-06-19 at 17:24 +0200, Daniel Vetter wrote:
>> On Fri, Jun 19, 2015 at 01:48:13PM +1000, Dave Airlie wrote:
>> > On 18 June 2015 at 16:04, Jani Nikula <jani.nikula@intel.com> wrote:
>> > >
>> > > Hi Dave, i915 fixes for drm-next/v4.2.
>> > >
>> > > BR,
>> > > Jani.
>> >
>> > And my gcc says:
>> >
>> > /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c:
>> > In function ‘__intel_set_mode’:
>> > /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c:11850:14:
>> > warning: ‘crtc_state’ may be used uninitialized in this function
>> > [-Wmaybe-uninitialized]
>> > return state->mode_changed || state->active_changed;
>> > ^
>> > /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c:11860:25:
>> > note: ‘crtc_state’ was declared here
>> > struct drm_crtc_state *crtc_state;
>> > ^
>> > /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c:11874:6:
>> > warning: ‘crtc’ may be used uninitialized in this function
>> > [-Wmaybe-uninitialized]
>> > if (crtc != intel_encoder->base.crtc)
>> > ^
>> > /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c:11859:19:
>> > note: ‘crtc’ was declared here
>> > struct drm_crtc *crtc;
>> > ^
>> >
>> > No idea if this is true, but I don't think I've seen it before now.
>> >
>> > gcc 5.1.1 on fedora 22
>>
>> Yeah this is new with Ander's patches. gcc Doesn't know that we have at
>> least 1 crtc and hence crtc&crtc are guaranteed to be initiliazed. I
>> think you should be able to shut it up with
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index e047105837c9..5ade250dc6d7 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -11856,8 +11856,8 @@ intel_modeset_update_state(struct drm_atomic_state *state)
>> struct drm_device *dev = state->dev;
>> struct drm_i915_private *dev_priv = dev->dev_private;
>> struct intel_encoder *intel_encoder;
>> - struct drm_crtc *crtc;
>> - struct drm_crtc_state *crtc_state;
>> + struct drm_crtc *crtc = NULL;
>> + struct drm_crtc_state *crtc_state = NULL;
>> struct drm_connector *connector;
>> int i;
>>
>> But the entire Finland team is out of office (celebrating solstice), so
>> might be better to wait for Monday for them to confirm. Otherwise just
>> apply this fixup with my ack if you want to send out the merge window pull
>> asap.
>>
>> Cheers, Daniel
>
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-22 8:12 UTC|newest]
Thread overview: 147+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 6:04 [PULL] drm-intel-next-fixes Jani Nikula
2015-06-19 3:48 ` Dave Airlie
2015-06-19 15:24 ` Daniel Vetter
2015-06-22 7:59 ` Ander Conselvan De Oliveira
2015-06-22 8:12 ` Jani Nikula [this message]
2015-06-22 8:13 ` Dave Airlie
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 7:53 Tvrtko Ursulin
2026-04-16 6:50 Tvrtko Ursulin
2026-02-20 8:31 Joonas Lahtinen
2026-02-13 10:53 Joonas Lahtinen
2026-02-05 8:02 Joonas Lahtinen
2026-01-29 8:11 Joonas Lahtinen
2026-01-22 8:02 Joonas Lahtinen
2025-08-05 7:48 Jani Nikula
2025-06-05 8:35 Joonas Lahtinen
2025-05-28 6:56 Joonas Lahtinen
2025-05-22 6:59 Joonas Lahtinen
2025-05-15 8:27 Joonas Lahtinen
2025-03-25 9:07 Jani Nikula
2024-11-21 8:37 Tvrtko Ursulin
2024-09-26 7:45 Joonas Lahtinen
2024-09-19 9:49 Joonas Lahtinen
2024-09-12 8:59 Joonas Lahtinen
2024-07-25 7:44 Tvrtko Ursulin
2024-07-18 9:30 Tvrtko Ursulin
2024-01-19 8:30 Joonas Lahtinen
2024-01-19 8:30 ` Joonas Lahtinen
2024-01-11 10:51 Joonas Lahtinen
2024-01-11 10:51 ` Joonas Lahtinen
2023-11-08 14:04 Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06 8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21 9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20 8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24 8:44 Tvrtko Ursulin
2022-03-17 7:47 Joonas Lahtinen
2022-03-10 7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2022-01-13 9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
2021-11-09 23:17 Rodrigo Vivi
2021-08-26 9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04 ` Rodrigo Vivi
2021-07-01 8:57 ` Jani Nikula
2021-02-25 14:43 Rodrigo Vivi
2021-02-18 22:46 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10 7:31 ` Dave Airlie
2020-08-12 12:49 ` Jani Nikula
2020-06-10 9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-04-02 21:30 Rodrigo Vivi
2020-03-27 8:16 Rodrigo Vivi
2019-12-05 9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-14 8:52 Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-09-27 19:49 Rodrigo Vivi
2019-09-19 14:16 Rodrigo Vivi
2019-09-11 23:33 Rodrigo Vivi
2019-05-15 7:48 Joonas Lahtinen
2019-05-09 10:01 Joonas Lahtinen
2019-05-02 13:40 Joonas Lahtinen
2019-04-30 7:08 Joonas Lahtinen
2019-04-25 6:13 Joonas Lahtinen
2019-03-12 20:55 Rodrigo Vivi
2018-12-27 7:40 Jani Nikula
2018-10-25 13:18 Joonas Lahtinen
2018-10-19 10:37 Joonas Lahtinen
2018-10-19 12:34 ` Daniel Vetter
2018-10-18 16:57 Joonas Lahtinen
2018-10-18 19:32 ` Daniel Vetter
2018-10-19 6:59 ` Joonas Lahtinen
2018-10-19 7:05 ` Daniel Vetter
2018-10-19 9:41 ` Joonas Lahtinen
2018-10-04 13:37 Joonas Lahtinen
2018-08-24 21:48 Rodrigo Vivi
2018-08-16 19:03 Rodrigo Vivi
2018-08-06 23:30 Rodrigo Vivi
2018-04-19 9:30 Joonas Lahtinen
2018-03-27 14:58 Joonas Lahtinen
2018-03-22 14:35 Joonas Lahtinen
2018-02-07 20:44 Rodrigo Vivi
2018-02-02 0:45 Rodrigo Vivi
2017-11-23 9:34 Jani Nikula
2017-11-10 13:21 Jani Nikula
2017-07-11 13:07 Jani Nikula
2017-06-27 8:28 Daniel Vetter
2017-02-17 9:46 Jani Nikula
2017-02-15 14:06 Jani Nikula
2016-12-22 10:22 Jani Nikula
2016-12-07 19:45 Jani Nikula
2016-10-11 14:09 Jani Nikula
2016-08-05 13:27 Jani Nikula
2016-07-25 6:41 Daniel Vetter
2016-05-25 8:57 Jani Nikula
2016-03-16 11:04 Jani Nikula
2016-01-14 20:06 Jani Nikula
2015-11-06 13:43 Jani Nikula
2015-10-22 8:28 Daniel Vetter
2015-09-02 11:49 Jani Nikula
2015-08-28 12:44 Jani Nikula
2015-08-16 18:13 Daniel Vetter
2015-07-02 11:26 Jani Nikula
2015-06-22 10:33 Jani Nikula
2015-06-11 8:40 Jani Nikula
2015-05-29 17:39 Daniel Vetter
2015-04-24 21:46 Jani Nikula
2015-04-15 12:21 Jani Nikula
2015-02-11 11:09 Jani Nikula
2015-02-11 11:48 ` Daniel Vetter
2014-12-30 12:47 Jani Nikula
2014-12-17 12:16 Jani Nikula
2014-12-11 13:43 Jani Nikula
2014-12-04 9:56 Daniel Vetter
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=878ubc2mcr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=conselvan2@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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 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.