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 v7 2/3] thunderbolt: Modify tb_nvm major and minor size.
Date: Mon, 29 Aug 2022 19:10:58 +0800 [thread overview]
Message-ID: <20220829111059.665305-3-chensiying21@gmail.com> (raw)
In-Reply-To: <20220829111059.665305-1-chensiying21@gmail.com>
From: Szuying Chen <Chloe_Chen@asmedia.com.tw>
The patch modify tb_nvm->major and tb_nvm->minor size to u32 that support
diffrent vendor's NVM version show.
Signed-off-by: Szuying Chen <Chloe_Chen@asmedia.com.tw>
---
Modify tb_nvm->major and tb_nvm->minor size to u32.
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 fc32737fcde4..9cf62d5f25d2 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-08-29 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 11:10 [PATCH v7 0/3] thunderbolt: add vendor's NVM formats Szuying Chen
2022-08-29 11:10 ` [PATCH v7 1/3] thunderbolt: Add vendor's specific operations of NVM Szuying Chen
2022-08-29 11:42 ` Greg KH
2022-08-30 13:45 ` Mika Westerberg
2022-08-29 11:10 ` Szuying Chen [this message]
2022-08-29 12:23 ` [PATCH v7 2/3] thunderbolt: Modify tb_nvm major and minor size Mario Limonciello
2022-08-29 11:10 ` [PATCH v7 3/3] thunderbolt: To extend ASMedia NVM formats Szuying Chen
2022-08-30 13:53 ` Mika Westerberg
2022-08-30 13:59 ` [PATCH v7 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=20220829111059.665305-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
all inboxes | Powered by JetHome®