From: Paolo Abeni <pabeni@redhat.com>
To: Wentao Liang <vulab@iscas.ac.cn>,
m.chetan.kumar@intel.com, loic.poulain@linaro.org,
ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: wwan: Add error handling for ipc_mux_dl_acb_send_cmds().
Date: Tue, 8 Apr 2025 12:34:50 +0200 [thread overview]
Message-ID: <89f9194a-e7dd-423b-ae54-c082f42edf51@redhat.com> (raw)
In-Reply-To: <20250405115236.2091-1-vulab@iscas.ac.cn>
On 4/5/25 1:52 PM, Wentao Liang wrote:
> The ipc_mux_dl_acbcmd_decode() calls the ipc_mux_dl_acb_send_cmds(),
> but does not report the error if ipc_mux_dl_acb_send_cmds() fails.
> This makes it difficult to detect command sending failures. A proper
> implementation can be found in ipc_mux_dl_cmd_decode().
>
> Add error reporting to the call, logging an error message using dev_err()
> if the command sending fails.
>
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
This has been posted while net-next was still closed for the merged
window.
You should have waited for the 'net-next is open' announcement on the
ML, or checked the status page, see:
https://elixir.bootlin.com/linux/v6.13.7/source/Documentation/process/maintainer-netdev.rst#L35
in the interest of fairness towards those who correctly wait
for the tree to be open I will ask you to repost this again,
in a couple of days.
When reposting, you can retain the already collected tags.
Thanks!
Paolo
prev parent reply other threads:[~2025-04-08 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 11:52 Wentao Liang
2025-04-06 12:25 ` Sergey Ryazanov
2025-04-08 10:34 ` Paolo Abeni [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=89f9194a-e7dd-423b-ae54-c082f42edf51@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@gmail.com \
--cc=vulab@iscas.ac.cn \
/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®