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>,
Utkarsh H Patel <utkarsh.h.patel@intel.com>
Subject: Re: [PATCH 0/3] thunderbolt: Few improvements for retimer access
Date: Mon, 12 Jun 2023 08:42:56 +0300 [thread overview]
Message-ID: <20230612054256.GR45886@black.fi.intel.com> (raw)
In-Reply-To: <20230602091055.65049-1-mika.westerberg@linux.intel.com>
On Fri, Jun 02, 2023 at 12:10:52PM +0300, Mika Westerberg wrote:
> Hi,
>
> These 3 patches improve the way we access retimers over sideband in
> various situations, and make it more compliant with the USB4 spec.
>
> Mika Westerberg (3):
> thunderbolt: Read retimer NVM authentication status prior tb_retimer_set_inbound_sbtx()
> thunderbolt: Do not send UNSET_INBOUND_SBTX when retimer NVM authentication started
> thunderbolt: Enable/disable sideband depending on USB4 port offline mode
All applied to thunderbolt.git/next.
Yehezkel, let me know if you have any objections or want more
clarifications.
prev parent reply other threads:[~2023-06-12 5:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 9:10 [PATCH 0/3] thunderbolt: Few improvements for retimer access Mika Westerberg
2023-06-02 9:10 ` [PATCH 1/3] thunderbolt: Read retimer NVM authentication status prior tb_retimer_set_inbound_sbtx() Mika Westerberg
2023-06-02 9:10 ` [PATCH 2/3] thunderbolt: Do not send UNSET_INBOUND_SBTX when retimer NVM authentication started Mika Westerberg
2023-06-02 9:10 ` [PATCH 3/3] thunderbolt: Enable/disable sideband depending on USB4 port offline mode Mika Westerberg
2023-06-03 19:24 ` Yehezkel Bernat
2023-06-04 5:11 ` Mika Westerberg
2023-06-04 9:16 ` Yehezkel Bernat
2023-06-05 6:19 ` Mika Westerberg
2023-06-12 5:42 ` 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=20230612054256.GR45886@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 \
--cc=utkarsh.h.patel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.