From: Luis Chamberlain <mcgrof@kernel.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-modules@vger.kernel.org, live-patching@vger.kernel.org,
fstests@vger.kernel.org, linux-block@vger.kernel.org,
hare@suse.de, dgilbert@interlog.com, jeyu@kernel.org,
osandov@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] libkmod-module: add support for a patient module removal option
Date: Mon, 15 Nov 2021 12:21:16 -0800 [thread overview]
Message-ID: <YZLBPGtm2vF2DsTk@bombadil.infradead.org> (raw)
In-Reply-To: <20210929184810.adrqpsvlfybnc5qt@ldmartin-desk2>
On Wed, Sep 29, 2021 at 11:48:31AM -0700, Lucas De Marchi wrote:
> > Sorry don't follow. And since I have one day before vacation, I suppose
> > I won't get to this until I get back. But I'd be happy if you massage
> > it as you see fit as you're used to the code base and I'm sure have
> > a better idea of what likely is best for the library.
>
>
> sure, np. I will take a look as time permits.
Just a friendly poke.
Luis
next prev parent reply other threads:[~2021-11-16 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 5:15 [PATCH v2 0/3] kmod: add patient module removal support Luis Chamberlain
2021-08-10 5:16 ` [PATCH v2 1/3] libkmod: add a library notice log level print Luis Chamberlain
2021-09-21 5:53 ` Lucas De Marchi
2021-09-21 18:40 ` Luis Chamberlain
2021-09-23 8:02 ` Lucas De Marchi
2021-08-10 5:16 ` [PATCH v2 2/3] libkmod/libkmod-module: add refcnt fd helper Luis Chamberlain
2021-08-10 5:16 ` [PATCH v2 3/3] libkmod-module: add support for a patient module removal option Luis Chamberlain
2021-09-23 8:51 ` Lucas De Marchi
2021-09-28 1:38 ` Luis Chamberlain
2021-09-29 18:48 ` Lucas De Marchi
2021-11-15 20:21 ` Luis Chamberlain [this message]
2021-12-08 12:53 ` Luis Chamberlain
2021-09-15 17:40 ` [PATCH v2 0/3] kmod: add patient module removal support Luis Chamberlain
2021-09-21 5:51 ` Lucas De Marchi
2022-02-17 8:13 ` Luis Chamberlain
2022-02-18 8:20 ` 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=YZLBPGtm2vF2DsTk@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=dgilbert@interlog.com \
--cc=fstests@vger.kernel.org \
--cc=hare@suse.de \
--cc=jeyu@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=osandov@fb.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).