From: Greg KH <gregkh@linuxfoundation.org>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
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,
rafael@kernel.org
Subject: Re: [PATCH v6 0/2] Remove useless param of devcoredump functions and fix bugs
Date: Fri, 10 Jun 2022 15:24:23 +0200 [thread overview]
Message-ID: <YqNGB5VitXvBWzzp@kroah.com> (raw)
In-Reply-To: <cover.1654569290.git.duoming@zju.edu.cn>
On Tue, Jun 07, 2022 at 11:26:24AM +0800, Duoming Zhou wrote:
> 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
Did you forget to cc: everyone on patch 2?
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-10 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 3:26 [PATCH v6 0/2] Remove useless param of devcoredump functions and fix bugs Duoming Zhou
2022-06-07 3:26 ` [PATCH v6 1/2] devcoredump: remove the useless gfp_t parameter in dev_coredumpv and dev_coredumpm Duoming Zhou
2022-06-10 13:25 ` Johannes Berg
2022-06-07 3:26 ` [PATCH v6 2/2] mwifiex: fix sleep in atomic context bugs caused by dev_coredumpv Duoming Zhou
2022-06-10 13:24 ` Greg KH [this message]
2022-06-10 13:27 ` [PATCH v6 0/2] Remove useless param of devcoredump functions and fix bugs Johannes Berg
2022-06-20 3:57 ` 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=YqNGB5VitXvBWzzp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=ganapathi017@gmail.com \
--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