From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: stern@rowland.harvard.edu
Cc: davem@davemloft.net, edumazet@google.com, greg@kroah.com,
jtornosm@redhat.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, oneukum@suse.com, pabeni@redhat.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] net: usb: ax88179_178a: avoid failed operations when device is disconnected
Date: Fri, 1 Dec 2023 18:27:14 +0100 [thread overview]
Message-ID: <20231201172716.182693-1-jtornosm@redhat.com> (raw)
In-Reply-To: <140e912f-8702-4e85-8d6c-ef0255e718f8@rowland.harvard.edu>
Hi Alan,
> Would it be good enough just to check for ret != -ENODEV and not do the
> stopping_unbinding check at all?
I thought about that but if possible, I would like to ignore the failed
operation messages only under a controlled and expected situation.
I think that if there is a problem with the device it will be easier to
analyze it later with all the possible information.
But this is my opinion ...
Thank you
Best regards
José Ignacio
next prev parent reply other threads:[~2023-12-01 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 15:16 [PATCH] net: usb: ax88179_178a: avoid failed operations when device is disconnected Jose Ignacio Tornos Martinez
2023-11-29 15:33 ` Oliver Neukum
2023-11-29 15:40 ` Alan Stern
2023-11-30 8:41 ` Jose Ignacio Tornos Martinez
2023-11-30 15:50 ` Alan Stern
2023-11-30 17:25 ` Jose Ignacio Tornos Martinez
2023-11-30 18:13 ` Alan Stern
2023-12-01 10:46 ` Jose Ignacio Tornos Martinez
2023-12-01 11:51 ` [PATCH v2] " Jose Ignacio Tornos Martinez
2023-12-01 12:25 ` Greg KH
2023-12-01 13:26 ` [PATCH v3] " Jose Ignacio Tornos Martinez
2023-12-01 16:13 ` Alan Stern
2023-12-01 17:27 ` Jose Ignacio Tornos Martinez [this message]
2023-12-01 20:14 ` Oliver Neukum
2023-12-04 11:31 ` Jose Ignacio Tornos Martinez
2023-12-05 13:51 ` [PATCH v4] " Jose Ignacio Tornos Martinez
2023-12-05 18:07 ` Alan Stern
2023-12-06 12:17 ` Jose Ignacio Tornos Martinez
2023-12-07 11:42 ` [PATCH v5] " Jose Ignacio Tornos Martinez
2023-12-07 16:41 ` Alan Stern
2023-12-07 17:50 ` [PATCH v6] " Jose Ignacio Tornos Martinez
2023-12-07 20:23 ` Alan Stern
2023-12-07 20:32 ` Jakub Kicinski
2023-12-08 4:56 ` Greg KH
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=20231201172716.182693-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=greg@kroah.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).