From: Szuying Chen <chensiying21@gmail.com>
To: gregkh@linuxfoundation.org, 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
Cc: Yd_Tseng@asmedia.com.tw, Chloe_Chen@asmedia.com.tw,
Richard_Hsu@asmedia.com.tw
Subject: [PATCH v8 2/3] thunderbolt: Modify tb_nvm major and minor size.
Date: Fri, 2 Sep 2022 17:40:09 +0800 [thread overview]
Message-ID: <20220902094010.2170-3-chensiying21@gmail.com> (raw)
In-Reply-To: <20220902094010.2170-1-chensiying21@gmail.com>
From: Szuying Chen <Chloe_Chen@asmedia.com.tw>
Intel's version can be stored in 2 bytes, but ASMedia's version
requires 8 bytes. Extend the 'major' and 'minor' members of the tb_nvm
structure to support both vendors.
Signed-off-by: Szuying Chen <Chloe_Chen@asmedia.com.tw>
---
v7->v8: Fix patch message based on suggestion by Mario
drivers/thunderbolt/tb.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thunderbolt/tb.h b/drivers/thunderbolt/tb.h
index 7ef571f88606..f3f834511983 100644
--- a/drivers/thunderbolt/tb.h
+++ b/drivers/thunderbolt/tb.h
@@ -50,8 +50,8 @@
*/
struct tb_nvm {
struct device *dev;
- u8 major;
- u8 minor;
+ u32 major;
+ u32 minor;
int id;
struct nvmem_device *active;
struct nvmem_device *non_active;
--
2.34.1
next prev parent reply other threads:[~2022-09-02 9:40 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 ` Szuying Chen [this message]
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 ` [PATCH v8 0/3] thunderbolt: add vendor's " Mika Westerberg
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=20220902094010.2170-3-chensiying21@gmail.com \
--to=chensiying21@gmail.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=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 \
--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