From: Greg KH <gregkh@linuxfoundation.org>
To: Szuying Chen <chensiying21@gmail.com>
Cc: mario.limonciello@amd.com, mika.westerberg@linux.intel.com,
andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Yd_Tseng@asmedia.com.tw,
Chloe_Chen@asmedia.com.tw, Richard_Hsu@asmedia.com.tw
Subject: Re: [PATCH v4] thunderbolt: thunderbolt: add vendor's NVM formats
Date: Tue, 16 Aug 2022 13:24:27 +0200 [thread overview]
Message-ID: <Yvt+a1kBLWmBgWXl@kroah.com> (raw)
In-Reply-To: <20220816105502.9059-1-chensiying21@gmail.com>
On Tue, Aug 16, 2022 at 06:55:02PM +0800, Szuying Chen wrote:
> @@ -527,6 +539,7 @@ int tb_port_state(struct tb_port *port)
> {
> struct tb_cap_phy phy;
> int res;
> +
> if (port->cap_phy == 0) {
> tb_port_WARN(port, "does not have a PHY\n");
> return -EINVAL;
> @@ -556,6 +569,7 @@ int tb_wait_for_port(struct tb_port *port, bool wait_if_unplugged)
> {
> int retries = 10;
> int state;
> +
> if (!port->cap_phy) {
> tb_port_WARN(port, "does not have PHY\n");
> return -EINVAL;
> @@ -653,6 +667,7 @@ int tb_port_add_nfc_credits(struct tb_port *port, int credits)
> int tb_port_clear_counter(struct tb_port *port, int counter)
> {
> u32 zero[3] = { 0, 0, 0 };
> +
> tb_port_dbg(port, "clearing counter %d\n", counter);
> return tb_port_write(port, zero, TB_CFG_COUNTERS, 3 * counter, 3);
> }
> @@ -875,6 +890,7 @@ static inline bool tb_switch_is_reachable(const struct tb_switch *parent,
> const struct tb_switch *sw)
> {
> u64 mask = (1ULL << parent->config.depth * 8) - 1;
> +
> return (tb_route(parent) & mask) == (tb_route(sw) & mask);
> }
>
These changes have nothing to do with your patch submission, and should
be a different patch entirely.
Remember, only do one-logical-thing per patch.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-16 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 10:55 [PATCH v4] thunderbolt: thunderbolt: add vendor's NVM formats Szuying Chen
2022-08-16 11:23 ` Greg KH
2022-08-16 11:24 ` Greg KH [this message]
2022-08-16 11:45 ` Mika Westerberg
2022-08-16 15:05 ` Limonciello, Mario
2022-08-17 0:20 ` kernel test robot
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=Yvt+a1kBLWmBgWXl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Chloe_Chen@asmedia.com.tw \
--cc=Richard_Hsu@asmedia.com.tw \
--cc=Yd_Tseng@asmedia.com.tw \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=chensiying21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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 NNTP newsgroup(s).