From: Greg KH <gregkh@linuxfoundation.org>
To: Szuying Chen <chensiying21@gmail.com>
Cc: 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] thunderbolt: thunderbolt: add vendor's NVM formats
Date: Wed, 10 Aug 2022 12:41:45 +0200 [thread overview]
Message-ID: <YvOLacO4H3ObAGL3@kroah.com> (raw)
In-Reply-To: <20220810101743.11214-1-chensiying21@gmail.com>
On Wed, Aug 10, 2022 at 06:17:43PM +0800, Szuying Chen wrote:
> The patch add tb_nvm_quirks() contain an array that has functions
> pointers to tb_nvm_vendor_apply().
> And tb_nvm_vendor_apply() that recognize supported vendor works in one
> of the following cases:
> Case NvmUpgradeSuppport: enable nvm's attribute by setting
> no_nvm_upgrade flag to create nvm_authenticate file node.
> Case NvmAdd:add active/non-active NVM devices.
> Case NvmWrite:update firmware to non-ative NVM device.
>
> Signed-off-by: Szuying Chen <chensiying21@gmail.com>
> ---
> drivers/thunderbolt/nvm.c | 59 ++++++++++++++----------------------
> drivers/thunderbolt/switch.c | 19 +++++++-----
> drivers/thunderbolt/tb.h | 18 +++++++----
> 3 files changed, 46 insertions(+), 50 deletions(-)
>
> diff --git a/drivers/thunderbolt/nvm.c b/drivers/thunderbolt/nvm.c
> index d5f283889da8..2aae8b3fa5dc 100644
> --- a/drivers/thunderbolt/nvm.c
> +++ b/drivers/thunderbolt/nvm.c
> @@ -14,6 +14,7 @@
> #include "tb.h"
>
> static DEFINE_IDA(nvm_ida);
> +
> static int tb_switch_nvm_read(void *priv, unsigned int offset, void *val,
> size_t bytes)
> {
> @@ -22,7 +23,6 @@ static int tb_switch_nvm_read(void *priv, unsigned int offset, void *val,
> int ret;
>
> pm_runtime_get_sync(&sw->dev);
> -
> if (!mutex_trylock(&sw->tb->lock)) {
> ret = restart_syscall();
> goto out;
These are odd whitespace changes that you do not discuss in your
changelog, which means we can't take this. Also, whitespace cleanups
should be in a separate commit.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-10 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 10:17 Szuying Chen
2022-08-10 10:41 ` Greg KH
2022-08-10 10:41 ` Greg KH [this message]
2022-08-10 10:56 ` Mika Westerberg
-- strict thread matches above, loose matches on Subject: below --
2022-08-15 4:11 Szuying Chen
2022-08-15 6:38 ` Greg KH
2022-08-15 6:40 ` Greg KH
2022-08-15 13:12 ` kernel test robot
2022-08-15 17:28 ` Limonciello, Mario
2022-08-15 19:20 ` Limonciello, Mario
2022-08-16 4:50 ` kernel test robot
2022-08-05 9:22 Szuying Chen
2022-08-05 9:31 ` Greg KH
2022-08-05 10:20 ` Mika Westerberg
2022-08-07 9:40 ` kernel test robot
2022-08-07 10:33 ` 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=YvOLacO4H3ObAGL3@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=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
all inboxes | Powered by JetHome®