From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: live-patching@vger.kernel.org, sjenning@redhat.com,
jkosina@suse.cz, vojtech@suse.cz, linux-kernel@vger.kernel.org,
Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH 1/2] livepatch: make kobject in klp_object statically allocated
Date: Tue, 19 May 2015 09:21:44 -0500 [thread overview]
Message-ID: <20150519142144.GA21359@treble.redhat.com> (raw)
In-Reply-To: <1432029679-9763-1-git-send-email-jslaby@suse.cz>
On Tue, May 19, 2015 at 12:01:18PM +0200, Jiri Slaby wrote:
> From: Miroslav Benes <mbenes@suse.cz>
>
> Make kobj variable (of type struct kobject) statically allocated in
> klp_object structure. It will allow us to move in the func-object-patch
> hierarchy through kobject links.
>
> The only reason to have it dynamic was to not have empty release
> callback in the code. However we have empty callbacks for function and
> patch in the code now, so it is no longer valid and the advantage of
> static allocation is clear.
>
> Signed-off-by: Miroslav Benes <mbenes@suse.cz>
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
next prev parent reply other threads:[~2015-05-19 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 10:01 [PATCH 1/2] livepatch: make kobject in klp_object statically allocated Jiri Slaby
2015-05-19 10:01 ` [PATCH 2/2] livepatch: introduce patch/func-walking helpers Jiri Slaby
2015-05-19 12:27 ` Minfei Huang
2015-05-19 21:58 ` Jiri Kosina
2015-05-20 1:51 ` Minfei Huang
2015-05-20 7:11 ` Jiri Slaby
2015-05-23 13:23 ` Minfei Huang
2015-05-19 14:22 ` Josh Poimboeuf
2015-05-19 21:59 ` Jiri Kosina
2015-05-19 14:21 ` Josh Poimboeuf [this message]
2015-05-19 21:59 ` [PATCH 1/2] livepatch: make kobject in klp_object statically allocated 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=20150519142144.GA21359@treble.redhat.com \
--to=jpoimboe@redhat.com \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.cz \
/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).