From: Duoming Zhou <duoming@zju.edu.cn>
To: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
briannorris@chromium.org
Cc: johannes@sipsolutions.net, rafael@kernel.org,
amitkarwar@gmail.com, ganapathi017@gmail.com,
sharvari.harisangam@nxp.com, huxinming820@gmail.com,
kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Duoming Zhou <duoming@zju.edu.cn>
Subject: [PATCH v8 0/2] Add new APIs of devcoredump and fix bugs
Date: Tue, 23 Aug 2022 19:21:25 +0800 [thread overview]
Message-ID: <cover.1661252818.git.duoming@zju.edu.cn> (raw)
The first patch adds new APIs to support migration of users
from old device coredump related APIs.
The second patch fix sleep in atomic context bugs of mwifiex
caused by dev_coredumpv().
Duoming Zhou (2):
devcoredump: add new APIs to support migration of users from old
device coredump related APIs
mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv
drivers/base/devcoredump.c | 116 ++++++++++++++++++
drivers/net/wireless/marvell/mwifiex/init.c | 9 +-
drivers/net/wireless/marvell/mwifiex/main.h | 3 +-
.../net/wireless/marvell/mwifiex/sta_event.c | 6 +-
include/linux/devcoredump.h | 34 +++++
5 files changed, 160 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2022-08-23 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 11:21 Duoming Zhou [this message]
2022-08-23 11:21 ` [PATCH v8 1/2] devcoredump: add new APIs to support migration of users from old device coredump related APIs Duoming Zhou
2022-08-23 11:21 ` [PATCH v8 2/2 RESEND] mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv Duoming Zhou
2022-09-22 6:08 ` Kalle Valo
2022-08-24 20:42 ` [PATCH v8 0/2] Add new APIs of devcoredump and fix bugs Brian Norris
2022-08-25 0:44 ` duoming
2022-08-25 5:59 ` Greg Kroah-Hartman
2022-08-25 6:59 ` duoming
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=cover.1661252818.git.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ganapathi017@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=huxinming820@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=sharvari.harisangam@nxp.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;
as well as URLs for NNTP newsgroup(s).