From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Szuying Chen <chensiying21@gmail.com>
Cc: gregkh@linuxfoundation.org, mario.limonciello@amd.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 v8 0/3] thunderbolt: add vendor's NVM formats
Date: Sun, 4 Sep 2022 14:45:46 +0300 [thread overview]
Message-ID: <YxSP6pxh99Ewgnvo@black.fi.intel.com> (raw)
In-Reply-To: <20220902094010.2170-1-chensiying21@gmail.com>
Hi Szuying Chen,
On Fri, Sep 02, 2022 at 05:40:07PM +0800, Szuying Chen wrote:
> From: Szuying Chen <Chloe_Chen@asmedia.com.tw>
>
> The patch series for vendors to extend their NVM format.
>
> v7->v8: The nvm_read() defined in tb.h. Modify
> tb_switch_nvm_validate() return value and no_nvm_upgrade bit setting.
>
> Szuying Chen (3):
> thunderbolt: Add vendor's specific operations of NVM
> thunderbolt: Modify tb_nvm major and minor size.
> thunderbolt: To extend ASMedia NVM formats.
Thanks for the patches. There are a couple of things I would still like
to change in this series but I can do those myself, and then I need to
run some testing to make sure Intel NVM formats still work.
No need to send a new version. Once I've done my modifications I will
post the updated series for review and perhaps you can then try on your
side that it still works on ASMedia hardware.
Thanks!
prev parent reply other threads:[~2022-09-04 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 9:40 [PATCH v8 0/3] thunderbolt: add vendor's NVM formats Szuying Chen
2022-09-02 9:40 ` [PATCH v8 1/3] thunderbolt: Add vendor's specific operations of NVM Szuying Chen
2022-09-04 0:03 ` kernel test robot
2022-09-02 9:40 ` [PATCH v8 2/3] thunderbolt: Modify tb_nvm major and minor size Szuying Chen
2022-09-02 9:40 ` [PATCH v8 3/3] thunderbolt: To extend ASMedia NVM formats Szuying Chen
2022-09-02 13:32 ` Limonciello, Mario
2022-09-04 11:39 ` Mika Westerberg
2022-09-04 11:45 ` 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=YxSP6pxh99Ewgnvo@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--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=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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 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.