From: patchwork-bot+netdevbpf@kernel.org
To: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, krishna.c.sudi@intel.com,
m.chetan.kumar@intel.com, linuxwwan@intel.com
Subject: Re: [PATCH net-next 0/2] net: wwan: debugfs dev reference not dropped
Date: Mon, 14 Feb 2022 14:20:10 +0000 [thread overview]
Message-ID: <164484841044.14634.18025566028520952249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220214071653.813010-1-m.chetan.kumar@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 14 Feb 2022 12:46:51 +0530 you wrote:
> This patch series contains WWAN subsystem & IOSM Driver changes to
> drop dev reference obtained as part of wwan debugfs dir entry retrieval.
>
> PATCH1: A new debugfs interface is introduced in wwan subsystem so
> that wwan driver can drop the obtained dev reference post debugfs use.
>
> PATCH2: IOSM Driver uses new debugfs interface to drop dev reference.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: wwan: debugfs obtained dev reference not dropped
https://git.kernel.org/netdev/net-next/c/76f05d88623e
- [net-next,2/2] net: wwan: iosm: drop debugfs dev reference
https://git.kernel.org/netdev/net-next/c/163f69ae22e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-14 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 7:16 [PATCH net-next 0/2] net: wwan: debugfs dev reference not dropped M Chetan Kumar
2022-02-14 7:16 ` [PATCH net-next 1/2] net: wwan: debugfs obtained " M Chetan Kumar
2022-02-14 7:16 ` [PATCH net-next 2/2] net: wwan: iosm: drop debugfs dev reference M Chetan Kumar
2022-02-14 14:20 ` patchwork-bot+netdevbpf [this message]
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=164484841044.14634.18025566028520952249.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=krishna.c.sudi@intel.com \
--cc=kuba@kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@gmail.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).