From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/4] thunderbolt: NVM fixes and consolidation
Date: Mon, 17 May 2021 14:59:03 +0300 [thread overview]
Message-ID: <20210517115907.52503-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
This series includes two fixes from Mathias on read side of NVM. These will
go to stable trees as well.
The rest will consolidate NVM read/write functions to get rid of the
duplication.
Mathias Nyman (2):
thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue
thunderbolt: usb4: Fix NVM read buffer bounds and offset issue
Mika Westerberg (2):
thunderbolt: Split NVM read/write generic functions out from usb4.c
thunderbolt: Use generic tb_nvm_[read|write]_data() for Thunderbolt 2/3 devices
drivers/thunderbolt/dma_port.c | 93 +++++-----------------------
drivers/thunderbolt/nvm.c | 95 ++++++++++++++++++++++++++++
drivers/thunderbolt/tb.h | 11 ++++
drivers/thunderbolt/usb4.c | 109 ++++++---------------------------
4 files changed, 139 insertions(+), 169 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-17 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 11:59 Mika Westerberg [this message]
2021-05-17 11:59 ` [PATCH 1/4] thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue Mika Westerberg
2021-05-20 8:54 ` Mika Westerberg
2021-05-17 11:59 ` [PATCH 2/4] thunderbolt: usb4: " Mika Westerberg
2021-05-20 8:54 ` Mika Westerberg
2021-05-17 11:59 ` [PATCH 3/4] thunderbolt: Split NVM read/write generic functions out from usb4.c Mika Westerberg
2021-05-31 11:38 ` Mika Westerberg
2021-05-17 11:59 ` [PATCH 4/4] thunderbolt: Use generic tb_nvm_[read|write]_data() for Thunderbolt 2/3 devices 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=20210517115907.52503-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mathias.nyman@linux.intel.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.