From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tang Bin <tangbin@cmss.chinamobile.com>,
Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/dp_mst: Fix drm_dp_mst_topology.c selftest compilation warning
Date: Tue, 14 Apr 2020 16:00:36 +0300 [thread overview]
Message-ID: <877dyimdcb.fsf@intel.com> (raw)
In-Reply-To: <ba9202f9-0373-52e7-9d74-4997e33c516d@cmss.chinamobile.com>
On Tue, 14 Apr 2020, Tang Bin <tangbin@cmss.chinamobile.com> wrote:
> But someone may query '{}' could not initialize all members, that's
> why I brought '{{{0}}}' up.
{} *does* initialize everything. What are you trying to say?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tang Bin <tangbin@cmss.chinamobile.com>,
Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/dp_mst: Fix drm_dp_mst_topology.c selftest compilation warning
Date: Tue, 14 Apr 2020 16:00:36 +0300 [thread overview]
Message-ID: <877dyimdcb.fsf@intel.com> (raw)
In-Reply-To: <ba9202f9-0373-52e7-9d74-4997e33c516d@cmss.chinamobile.com>
On Tue, 14 Apr 2020, Tang Bin <tangbin@cmss.chinamobile.com> wrote:
> But someone may query '{}' could not initialize all members, that's
> why I brought '{{{0}}}' up.
{} *does* initialize everything. What are you trying to say?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2020-04-14 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 14:17 [PATCH] drm/dp_mst: Fix drm_dp_mst_topology.c selftest compilation warning Tang Bin
2020-04-11 14:17 ` Tang Bin
2020-04-13 14:08 ` Alex Deucher
2020-04-13 14:08 ` Alex Deucher
2020-04-14 11:08 ` Jani Nikula
2020-04-14 11:08 ` Jani Nikula
2020-04-14 12:39 ` Tang Bin
2020-04-14 13:00 ` Jani Nikula [this message]
2020-04-14 13:00 ` Jani Nikula
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=877dyimdcb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tangbin@cmss.chinamobile.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.