From: Lucas De Marchi <lucas.demarchi@intel.com>
To: linux-modules@vger.kernel.org
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH 0/4] modprobe -r fixes and refactors
Date: Tue, 29 Mar 2022 02:05:34 -0700 [thread overview]
Message-ID: <20220329090540.38255-1-lucas.demarchi@intel.com> (raw)
Fixes and refactors that I noticed were needed while preparing support
for "patient module removal[1][2]" in modprobe.
The added functionality will be sent on top of these.
[1] https://lore.kernel.org/linux-modules/20210803202417.462197-1-mcgrof@kernel.org/
[2] https://lore.kernel.org/linux-modules/20210810051602.3067384-1-mcgrof@kernel.org/
Lucas De Marchi (4):
modprobe: Rename rmmod_do_deps_list
modprobe: Fix holders removal
modprobe: Move check for remove_holders to caller
modprobe: Make rmmod_do_module() contain all the removal sequence
tools/modprobe.c | 64 ++++++++++++++++++++++++++++--------------------
1 file changed, 38 insertions(+), 26 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-29 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:05 Lucas De Marchi [this message]
2022-03-29 9:05 ` [PATCH 1/4] modprobe: Rename rmmod_do_deps_list Lucas De Marchi
2022-03-29 19:37 ` Luis Chamberlain
2022-03-29 9:05 ` [PATCH 1/4] modprobe: rename rmmod_do_deps_list Lucas De Marchi
2022-03-29 9:05 ` [PATCH 2/4] modprobe: Fix holders removal Lucas De Marchi
2022-04-06 22:20 ` Luis Chamberlain
2022-03-29 9:05 ` [PATCH 3/4] modprobe: Move check for remove_holders to caller Lucas De Marchi
2022-04-06 22:21 ` Luis Chamberlain
2022-03-29 9:05 ` [PATCH 3/4] modprobe: move " Lucas De Marchi
2022-03-29 9:05 ` [PATCH 4/4] modprobe: Make rmmod_do_module() contain all the removal sequence Lucas De Marchi
2022-04-06 22:22 ` Luis Chamberlain
2022-04-07 5:05 ` Lucas De Marchi
2022-03-29 9:09 ` [PATCH 0/4] modprobe -r fixes and refactors Lucas De Marchi
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=20220329090540.38255-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
/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.