From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>
Subject: Re: [PATCH] thunderbolt: Use correct error code with ERROR_NOT_SUPPORTED
Date: Fri, 19 Apr 2024 08:03:43 +0300 [thread overview]
Message-ID: <20240419050343.GS112498@black.fi.intel.com> (raw)
In-Reply-To: <20240415065528.576769-1-mika.westerberg@linux.intel.com>
On Mon, Apr 15, 2024 at 09:55:28AM +0300, Mika Westerberg wrote:
> We check for -EOPNOTSUPP but tb_xdp_handle_error() translated it to
> -ENOTSUPP instead which is dealt as "transient" error and retried after
> a while. Fix this so that we bail out early when the other side clearly
> tells us it is does not support this.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied to thunderbolt.git/next.
prev parent reply other threads:[~2024-04-19 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 6:55 [PATCH] thunderbolt: Use correct error code with ERROR_NOT_SUPPORTED Mika Westerberg
2024-04-19 5:03 ` Mika Westerberg [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=20240419050343.GS112498@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).