From: Joe Lawrence <joe.lawrence@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
live-patching@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v4 06/10] modpost: Add modinfo flag to livepatch modules
Date: Mon, 19 Aug 2019 12:02:25 -0400 [thread overview]
Message-ID: <42254ffc-6422-19e1-62a2-6abc23fd089a@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1908190928520.31051@pobox.suse.cz>
On 8/19/19 3:31 AM, Miroslav Benes wrote:
> On Mon, 19 Aug 2019, Masahiro Yamada wrote:
>
>>
>> I can review this series from the build system point of view,
>> but I am not familiar enough with live-patching itself.
>>
>> Some possibilities:
>>
>> [1] Merge this series thru the live-patch tree after the
>> kbuild base patches land.
>> This requires one extra development cycle (targeting for 5.5-rc1)
>> but I think this is the official way if you do not rush into it.
>
> I'd prefer this option. There is no real rush and I think we can wait one
> extra development cycle.
Agreed. I'm in no hurry and was only curious about the kbuild changes
that this patchset is now dependent on -- how to note them for other
reviewers or anyone wishing to test.
> Joe, could you submit one more revision with all the recent changes (once
> kbuild improvements settle down), please? We should take a look at the
> whole thing one more time? What do you think?
>
Definitely, yes. I occasionally force a push to:
https://github.com/joe-lawrence/linux/tree/klp-convert-v5-expanded
as I've been updating and collecting feedback from v4. Once updates
settle, I'll send out a new v5 set.
-- Joe
next prev parent reply other threads:[~2019-08-19 16:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190509143859.9050-1-joe.lawrence@redhat.com>
[not found] ` <alpine.LSU.2.21.1906131451560.22698@pobox.suse.cz>
[not found] ` <b1a627a4-3702-9689-6c03-0c2123c06a2d@redhat.com>
[not found] ` <c9021573-11c6-b576-0aa6-97754c98a06e@redhat.com>
[not found] ` <20190614083435.uq3mk6mprbatysol@pathway.suse.cz>
2019-06-25 11:36 ` [PATCH v4 00/10] klp-convert livepatch build tooling Miroslav Benes
2019-06-25 13:24 ` Joe Lawrence
2019-06-25 19:08 ` Joe Lawrence
2019-06-26 10:27 ` Miroslav Benes
[not found] ` <20190509143859.9050-4-joe.lawrence@redhat.com>
2019-07-31 2:50 ` [PATCH v4 03/10] livepatch: Add klp-convert tool Masahiro Yamada
2019-07-31 3:36 ` Masahiro Yamada
2019-08-09 18:42 ` Joe Lawrence
2019-08-13 1:15 ` Masahiro Yamada
[not found] ` <20190509143859.9050-7-joe.lawrence@redhat.com>
2019-07-31 5:58 ` [PATCH v4 06/10] modpost: Add modinfo flag to livepatch modules Masahiro Yamada
2019-08-12 15:56 ` Joe Lawrence
2019-08-15 15:05 ` Masahiro Yamada
2019-08-16 8:19 ` Miroslav Benes
2019-08-16 12:43 ` Joe Lawrence
2019-08-16 19:01 ` Joe Lawrence
2019-08-19 3:50 ` Masahiro Yamada
2019-08-19 15:55 ` Joe Lawrence
2019-08-20 7:54 ` Miroslav Benes
2019-08-19 3:49 ` Masahiro Yamada
2019-08-19 7:31 ` Miroslav Benes
2019-08-19 16:02 ` Joe Lawrence [this message]
2019-08-22 3:35 ` Masahiro Yamada
2019-08-13 10:26 ` Miroslav Benes
[not found] ` <20190509143859.9050-8-joe.lawrence@redhat.com>
2019-08-16 11:35 ` [PATCH v4 07/10] livepatch: Add sample livepatch module Masahiro Yamada
2019-08-16 12:47 ` Joe Lawrence
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=42254ffc-6422-19e1-62a2-6abc23fd089a@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=yamada.masahiro@socionext.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).