From: Kalle Valo <kvalo@kernel.org>
To: cgel.zte@gmail.com
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
gregkh@linuxfoundation.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Minghao Chi <chi.minghao@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] wlcore: using pm_runtime_resume_and_get instead of pm_runtime_get_sync
Date: Tue, 12 Apr 2022 12:33:36 +0300 [thread overview]
Message-ID: <8735iiprwv.fsf@kernel.org> (raw)
In-Reply-To: <20220412091742.2533527-1-chi.minghao@zte.com.cn> (cgel zte's message of "Tue, 12 Apr 2022 09:17:42 +0000")
cgel.zte@gmail.com writes:
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> Using pm_runtime_resume_and_get is more appropriate
> for simplifing code
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
Please try to make the patch titles unique, you have already submitted a
patch with the same name:
wlcore: using pm_runtime_resume_and_get instead of pm_runtime_get_sync
https://patchwork.kernel.org/project/linux-wireless/patch/20220408081205.2494512-1-chi.minghao@zte.com.cn/
I'll rename this patch to:
wlcore: main: use pm_runtime_resume_and_get() instead of pm_runtime_get_sync()
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-12 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:17 [PATCH] wlcore: using pm_runtime_resume_and_get instead of pm_runtime_get_sync cgel.zte
2022-04-12 9:33 ` Kalle Valo [this message]
2022-04-23 7:08 ` wlcore: main: use pm_runtime_resume_and_get() instead of pm_runtime_get_sync() Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 8:12 [PATCH] wlcore: using pm_runtime_resume_and_get instead of pm_runtime_get_sync cgel.zte
2022-04-12 9:34 ` Kalle Valo
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=8735iiprwv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zealci@zte.com.cn \
/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.