From: Duoming Zhou <duoming@zju.edu.cn>
To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Cc: briannorris@chromium.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,
netdev@vger.kernel.org, johannes@sipsolutions.net,
gregkh@linuxfoundation.org, rafael@kernel.org,
Duoming Zhou <duoming@zju.edu.cn>
Subject: [PATCH v7 0/2] Remove useless param of devcoredump functions and fix bugs
Date: Wed, 17 Aug 2022 20:39:11 +0800 [thread overview]
Message-ID: <cover.1660739276.git.duoming@zju.edu.cn> (raw)
The first patch removes the extra gfp_t param of dev_coredumpv()
and dev_coredumpm().
The second patch fix sleep in atomic context bugs of mwifiex
caused by dev_coredumpv().
Duoming Zhou (2):
devcoredump: remove the useless gfp_t parameter in dev_coredumpv and
dev_coredumpm
mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv
drivers/base/devcoredump.c | 16 ++++++----------
drivers/bluetooth/btmrvl_sdio.c | 2 +-
drivers/bluetooth/hci_qca.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +-
drivers/gpu/drm/etnaviv/etnaviv_dump.c | 2 +-
drivers/gpu/drm/msm/disp/msm_disp_snapshot.c | 4 ++--
drivers/gpu/drm/msm/msm_gpu.c | 4 ++--
drivers/media/platform/qcom/venus/core.c | 2 +-
drivers/net/can/spi/mcp251xfd/mcp251xfd-dump.c | 2 +-
drivers/net/wireless/ath/ath10k/coredump.c | 2 +-
.../net/wireless/ath/wil6210/wil_crash_dump.c | 2 +-
.../wireless/broadcom/brcm80211/brcmfmac/debug.c | 2 +-
drivers/net/wireless/intel/iwlwifi/fw/dbg.c | 6 ++----
drivers/net/wireless/marvell/mwifiex/init.c | 9 +++++----
drivers/net/wireless/marvell/mwifiex/main.c | 3 +--
drivers/net/wireless/marvell/mwifiex/main.h | 3 ++-
drivers/net/wireless/marvell/mwifiex/sta_event.c | 6 +++---
drivers/net/wireless/mediatek/mt76/mt7615/mac.c | 3 +--
drivers/net/wireless/mediatek/mt76/mt7921/mac.c | 3 +--
drivers/net/wireless/realtek/rtw88/main.c | 2 +-
drivers/net/wireless/realtek/rtw89/ser.c | 2 +-
drivers/remoteproc/qcom_q6v5_mss.c | 2 +-
drivers/remoteproc/remoteproc_coredump.c | 8 ++++----
include/drm/drm_print.h | 2 +-
include/linux/devcoredump.h | 13 ++++++-------
sound/soc/intel/avs/apl.c | 2 +-
sound/soc/intel/avs/skl.c | 2 +-
sound/soc/intel/catpt/dsp.c | 2 +-
28 files changed, 51 insertions(+), 59 deletions(-)
--
2.17.1
next reply other threads:[~2022-08-17 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 12:39 Duoming Zhou [this message]
2022-08-17 12:39 ` [PATCH v7 1/2] devcoredump: remove the useless gfp_t parameter in dev_coredumpv and dev_coredumpm Duoming Zhou
2022-08-17 12:43 ` Greg KH
2022-08-17 14:05 ` duoming
2022-08-18 14:58 ` Greg KH
2022-08-18 15:46 ` duoming
2022-08-22 18:21 ` Brian Norris
2022-08-23 11:26 ` duoming
2022-08-17 12:39 ` [PATCH v7 2/2 RESEND] mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv Duoming Zhou
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.1660739276.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).