From: Umang Jain <umang.jain@ideasonboard.com>
To: Stefan Wahren <wahrenst@gmx.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
kernel-list@raspberrypi.com
Subject: Re: [PATCH 2/8] staging: vchiq_core: Properly log dev_err()
Date: Fri, 11 Oct 2024 16:18:08 +0530 [thread overview]
Message-ID: <9ed1ca9d-a17e-46b7-ae08-81c3d44a6063@ideasonboard.com> (raw)
In-Reply-To: <b0074647-f730-4d94-a11c-ebec7f48b928@gmx.net>
Hi Stefan
On 11/10/24 4:15 pm, Stefan Wahren wrote:
> Hi Umang,
>
> [add Raspberry Pi guys to the loop]
>
> Am 11.10.24 um 09:22 schrieb Umang Jain:
>> Properly log a dev_err() message when the msgid is not of
>> VCHIQ_MSG_PADDING type. Drop 'oldmsgid' scoped variable and improve
>> on the error string as well.
>>
>> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
>> ---
>> .../vc04_services/interface/vchiq_arm/vchiq_core.c | 11 ++++-------
>> 1 file changed, 4 insertions(+), 7 deletions(-)
>>
>> diff --git
>> a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
>> b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
>> index e9b60dd8d419..1dca676186b6 100644
>> --- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
>> +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c
>> @@ -1188,13 +1188,10 @@ queue_message_sync(struct vchiq_state *state,
>> struct vchiq_service *service,
>> header = (struct vchiq_header *)SLOT_DATA_FROM_INDEX(state,
>> local->slot_sync);
>>
>> - {
>> - int oldmsgid = header->msgid;
>> -
>> - if (oldmsgid != VCHIQ_MSGID_PADDING)
>> - dev_err(state->dev, "core: %d: qms - msgid %x, not
>> PADDING\n",
>> - state->id, oldmsgid);
>> - }
>> + if (header->msgid != VCHIQ_MSGID_PADDING)
>> + dev_err(state->dev,
>> + "core: %d: qms - msgid %x, is not a PADDING message\n",
>> + state->id, header->msgid);
> I'm fine with this change, but the behavior looks strange to me.
>
> Either this is a real error, I would expect the function would return
> with something like EINVAL here or this should be a warning?
>
> Sorry, no idea what's correct here.
indeed, I'll check the code path and see how it is used.
However, I will propose the change (if any) on top of this series/patch.
Since it would be functional change ... so need to document it
appropriately.
>
> Best regards
>>
>> dev_dbg(state->dev, "sync: %d: qms %s@%pK,%x (%d->%d)\n",
>> state->id, msg_type_str(VCHIQ_MSG_TYPE(msgid)), header, size,
>
next prev parent reply other threads:[~2024-10-11 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 7:22 [PATCH 0/8] staging: vchiq: Lower indentation at various places Umang Jain
2024-10-11 7:22 ` [PATCH 1/8] staging: vchiq_core: Locally cache cache_line_size information Umang Jain
2024-10-11 7:22 ` [PATCH 2/8] staging: vchiq_core: Properly log dev_err() Umang Jain
2024-10-11 10:45 ` Stefan Wahren
2024-10-11 10:48 ` Umang Jain [this message]
2024-10-11 7:22 ` [PATCH 3/8] staging: vchiq_core: Do not log debug in a separate scope Umang Jain
2024-10-11 10:47 ` Stefan Wahren
2024-10-11 7:22 ` [PATCH 4/8] staging: vchiq_core: Lower indentation of a conditional block Umang Jain
2024-10-11 10:54 ` Stefan Wahren
2024-10-11 7:22 ` [PATCH 5/8] staging: vchiq_core: Indent copy_message_data() on a single line Umang Jain
2024-10-11 10:55 ` Stefan Wahren
2024-10-11 7:22 ` [PATCH 6/8] staging: vchiq_arm: Lower indentation of a conditional block Umang Jain
2024-10-11 11:05 ` Stefan Wahren
2024-10-11 7:22 ` [PATCH 7/8] staging: vchiq_core: Lower indentation in parse_open() Umang Jain
2024-10-11 11:07 ` Stefan Wahren
2024-10-11 7:22 ` [PATCH 8/8] staging: vchiq_core: Lower indentation in vchiq_close_service_internal Umang Jain
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=9ed1ca9d-a17e-46b7-ae08-81c3d44a6063@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=wahrenst@gmx.net \
/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®