From: Jiri Kosina <jikos@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>,
jeyu@kernel.org, pmladek@suse.com, lpechacek@suse.cz,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] livepatch: force transition to finish
Date: Tue, 21 Nov 2017 00:17:46 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1711210017240.32604@cbobk.fhfr.pm> (raw)
In-Reply-To: <20171120231429.GA13906@amd>
On Tue, 21 Nov 2017, Pavel Machek wrote:
> Just disable rmmod in case of forced removal.
Yeah, well, that's basically what the patch does :)
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2017-11-20 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 13:50 [PATCH v4 0/2] livepatch: Introduce signal and force sysfs attributes Miroslav Benes
2017-11-15 13:50 ` [PATCH v4 1/2] livepatch: send a fake signal to all blocking tasks Miroslav Benes
2017-11-30 21:53 ` Jiri Kosina
2017-12-01 10:13 ` Michael Ellerman
2017-11-15 13:50 ` [PATCH v4 2/2] livepatch: force transition to finish Miroslav Benes
2017-11-20 15:57 ` Miroslav Benes
2017-11-20 23:02 ` Josh Poimboeuf
2017-11-20 23:09 ` Jiri Kosina
2017-11-20 23:11 ` Jiri Kosina
2017-11-20 23:14 ` Josh Poimboeuf
2017-11-22 10:29 ` [PATCH v4.1 " Miroslav Benes
2017-12-15 18:04 ` Jason Baron
2017-12-18 13:23 ` Miroslav Benes
2017-12-18 19:30 ` Josh Poimboeuf
2017-12-19 13:27 ` Petr Mladek
2017-11-20 23:14 ` [PATCH v4 " Pavel Machek
2017-11-20 23:17 ` Jiri Kosina [this message]
2017-11-21 10:04 ` Petr Mladek
2017-11-16 1:16 ` [PATCH v4 0/2] livepatch: Introduce signal and force sysfs attributes Josh Poimboeuf
2017-12-04 21:37 ` Jiri Kosina
2017-12-07 12:23 ` Jiri Kosina
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=nycvar.YFH.7.76.1711210017240.32604@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=jeyu@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lpechacek@suse.cz \
--cc=mbenes@suse.cz \
--cc=pavel@ucw.cz \
--cc=pmladek@suse.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).