From: Harry Wentland <hwentlan@amd.com>
To: "Liu, Zhan" <Zhan.Liu@amd.com>, Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu/display: add fallthrough comment
Date: Thu, 5 Dec 2019 19:16:31 -0500 [thread overview]
Message-ID: <efca0db3-ba0e-31ce-18fb-aefc4281d466@amd.com> (raw)
In-Reply-To: <DM6PR12MB3466E0D8A51B36AAA10202479E5C0@DM6PR12MB3466.namprd12.prod.outlook.com>
On 2019-12-05 5:16 p.m., Liu, Zhan wrote:
>
>
>> -----Original Message-----
>> From: Alex Deucher <alexdeucher@gmail.com>
>> Sent: 2019/December/05, Thursday 5:13 PM
>> To: Liu, Zhan <Zhan.Liu@amd.com>
>> Cc: amd-gfx@lists.freedesktop.org; Deucher, Alexander
>> <Alexander.Deucher@amd.com>
>> Subject: Re: [PATCH] drm/amdgpu/display: add fallthrough comment
>>
>> On Thu, Dec 5, 2019 at 5:10 PM Liu, Zhan <Zhan.Liu@amd.com> wrote:
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> On Behalf Of
>>>> Alex Deucher
>>>> Sent: 2019/December/05, Thursday 4:39 PM
>>>> To: amd-gfx@lists.freedesktop.org
>>>> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>
>>>> Subject: [PATCH] drm/amdgpu/display: add fallthrough comment
>>>>
>>>> To avoid a compiler warning.
>>>>
>>>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>>>> ---
>>>> drivers/gpu/drm/amd/display/dc/dce/dce_aux.c | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/amd/display/dc/dce/dce_aux.c
>>>> b/drivers/gpu/drm/amd/display/dc/dce/dce_aux.c
>>>> index 191b68b8163a..f1a5d2c6aa37 100644
>>>> --- a/drivers/gpu/drm/amd/display/dc/dce/dce_aux.c
>>>> +++ b/drivers/gpu/drm/amd/display/dc/dce/dce_aux.c
>>>> @@ -645,6 +645,7 @@ bool dce_aux_transfer_with_retries(struct
>>>> ddc_service *ddc,
>>>> case AUX_TRANSACTION_REPLY_AUX_DEFER:
>>>> case
>>>> AUX_TRANSACTION_REPLY_I2C_OVER_AUX_DEFER:
>>>> retry_on_defer = true;
>>>> + /* fall through */
>>>
>>> I am a bit confusing here. Why a comment can avoid a compiler warning?
>>
>> The kernel enables fall through warnings, so unless there is a comment
>> mentioning that are are expecting to fall through here, we get a warning.
>> The idea is to find missing breaks in switch code.
>>
>> Alex
>
> Got you. Thank you for your explanation.
>
> Reviewed-by: Zhan Liu <zhan.liu@amd.com>
>
Interesting. It's described at [1] (search for
-Wimplicit-fallthrough=3). Never knew that.
This is also
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
[1]
https://developers.redhat.com/blog/2017/03/10/wimplicit-fallthrough-in-gcc-7/
Harry
>>
>>>
>>>> case
>>>> AUX_TRANSACTION_REPLY_I2C_OVER_AUX_NACK:
>>>> if (++aux_defer_retries >=
>>>> AUX_MAX_DEFER_RETRIES) {
>>>> goto fail;
>>>> --
>>>> 2.23.0
>>>>
>>>> _______________________________________________
>>>> amd-gfx mailing list
>>>> amd-gfx@lists.freedesktop.org
>>>>
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.
>>>> freedesktop.org%2Fmailman%2Flistinfo%2Famd-
>>>>
>> gfx&data=02%7C01%7Czhan.liu%40amd.com%7C77d85a0275aa4c0a78
>>>>
>> 2f08d779cb9716%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C6
>>>>
>> 37111788208702340&sdata=3m%2FuNuNIgq82z%2BAeXJ9y7wn81kV%
>>>> 2FiDt3AyC3CDiTRrc%3D&reserved=0
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2019-12-06 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 21:39 [PATCH] drm/amdgpu/display: add fallthrough comment Alex Deucher
2019-12-05 22:10 ` Liu, Zhan
2019-12-05 22:12 ` Alex Deucher
2019-12-05 22:16 ` Liu, Zhan
2019-12-06 0:16 ` Harry Wentland [this message]
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=efca0db3-ba0e-31ce-18fb-aefc4281d466@amd.com \
--to=hwentlan@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Zhan.Liu@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-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