All of lore.kernel.org
 help / color / mirror / Atom feed
From: M Chetan Kumar <m.chetan.kumar@linux.intel.com>
To: netdev@vger.kernel.org
Cc: 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,
	m.chetan.kumar@linux.intel.com, linuxwwan@intel.com
Subject: [PATCH net-next 0/2] net: wwan: debugfs dev reference not dropped
Date: Mon, 14 Feb 2022 12:46:51 +0530	[thread overview]
Message-ID: <20220214071653.813010-1-m.chetan.kumar@linux.intel.com> (raw)

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.

Please refer to commit messages for details.

M Chetan Kumar (2):
  net: wwan: debugfs obtained dev reference not dropped
  net: wwan: iosm: drop debugfs dev reference

 drivers/net/wwan/iosm/iosm_ipc_debugfs.c |  5 ++--
 drivers/net/wwan/iosm/iosm_ipc_imem.h    |  2 ++
 drivers/net/wwan/wwan_core.c             | 35 ++++++++++++++++++++++++
 include/linux/wwan.h                     |  2 ++
 4 files changed, 42 insertions(+), 2 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-02-14  7:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  7:16 M Chetan Kumar [this message]
2022-02-14  7:16 ` [PATCH net-next 1/2] net: wwan: debugfs obtained dev reference not dropped 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 ` [PATCH net-next 0/2] net: wwan: debugfs dev reference not dropped patchwork-bot+netdevbpf

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=20220214071653.813010-1-m.chetan.kumar@linux.intel.com \
    --to=m.chetan.kumar@linux.intel.com \
    --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=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 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.