From: Harry Wentland <harry.wentland@amd.com>
To: Tom Rix <trix@redhat.com>,
sunpeng.li@amd.com, Rodrigo.Siqueira@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@linux.ie, daniel@ffwll.ch,
wenjing.liu@amd.com, waynelin@amd.com, Anson.Jacob@amd.com,
Yu-ting.Shen@amd.com, keescook@chromium.org,
nicholas.kazlauskas@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/display: cleanup extern usage in function definition
Date: Mon, 4 Apr 2022 11:57:08 -0400 [thread overview]
Message-ID: <e0397927-06fc-933e-f73a-794e0629e0fd@amd.com> (raw)
In-Reply-To: <462e2f2a-0cc8-2e2e-93b6-504cc12aa768@redhat.com>
On 2022-04-04 11:43, Tom Rix wrote:
>
> On 4/4/22 8:22 AM, Harry Wentland wrote:
>>
>> On 2022-04-03 10:21, Tom Rix wrote:
>>> Smatch reports this issue
>>> hdcp1_execution.c:500:29: warning: function
>>> 'mod_hdcp_hdcp1_dp_execution' with external linkage
>>> has definition
>>>
>> Which branch are you using?
>
> linux-next from 4/1
>
Apologies. I was looking at the wrong function.
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> Tom
>
>>
>> I don't see the 'extern' on
>> https://gitlab.freedesktop.org/agd5f/linux/-/blob/amd-staging-drm-next/drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c>>>
>> Harry
>>
>>
>>> The storage-class-specifier extern is not needed in a
>>> definition, so remove it.
>>>
>>> Signed-off-by: Tom Rix <trix@redhat.com>
>>> ---
>>> drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c b/drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c
>>> index 6ec918af3bff..1ddb4f5eac8e 100644
>>> --- a/drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c
>>> +++ b/drivers/gpu/drm/amd/display/modules/hdcp/hdcp1_execution.c
>>> @@ -497,9 +497,9 @@ enum mod_hdcp_status mod_hdcp_hdcp1_execution(struct mod_hdcp *hdcp,
>>> return status;
>>> }
>>> -extern enum mod_hdcp_status mod_hdcp_hdcp1_dp_execution(struct mod_hdcp *hdcp,
>>> - struct mod_hdcp_event_context *event_ctx,
>>> - struct mod_hdcp_transition_input_hdcp1 *input)
>>> +enum mod_hdcp_status mod_hdcp_hdcp1_dp_execution(struct mod_hdcp *hdcp,
>>> + struct mod_hdcp_event_context *event_ctx,
>>> + struct mod_hdcp_transition_input_hdcp1 *input)
>>> {
>>> enum mod_hdcp_status status = MOD_HDCP_STATUS_SUCCESS;
>>>
>
next prev parent reply other threads:[~2022-04-04 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 14:21 Tom Rix
2022-04-04 15:22 ` Harry Wentland
2022-04-04 15:43 ` Tom Rix
2022-04-04 15:57 ` Harry Wentland [this message]
2022-04-07 17:28 ` Alex Deucher
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=e0397927-06fc-933e-f73a-794e0629e0fd@amd.com \
--to=harry.wentland@amd.com \
--cc=Anson.Jacob@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=Yu-ting.Shen@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicholas.kazlauskas@amd.com \
--cc=sunpeng.li@amd.com \
--cc=trix@redhat.com \
--cc=waynelin@amd.com \
--cc=wenjing.liu@amd.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
all inboxes | Powered by JetHome®