From: Luis Chamberlain <mcgrof@kernel.org>
To: Maninder Singh <maninder1.s@samsung.com>,
Vimal Agrawal <avimalin@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"wedsonaf@google.com" <wedsonaf@google.com>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"christophe.leroy@csgroup.eu" <christophe.leroy@csgroup.eu>,
"swboyd@chromium.org" <swboyd@chromium.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"gary@garyguo.net" <gary@garyguo.net>,
"mbenes@suse.cz" <mbenes@suse.cz>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"void@manifault.com" <void@manifault.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vaneet Narang <v.narang@samsung.com>,
Onkarnath <onkarnath.1@samsung.com>
Subject: Re: [PATCH 1/1] kallsyms: add kallsyms_show_value definition in all cases
Date: Wed, 20 Apr 2022 08:21:38 -0700 [thread overview]
Message-ID: <YmAlAvy6aSeeJKoO@bombadil.infradead.org> (raw)
In-Reply-To: <747830777.1512786.1650256482294@mail-kr5-3>
On Mon, Apr 18, 2022 at 10:04:42AM +0530, Maninder Singh wrote:
> > What about splitting kallsyms.c into two source files where one
> > would be always compiled? It would be usable also for the
> > spring function introduced by
> > https://lore.kernel.org/r/20220323164742.2984281-1-maninder1.s@samsung.com
> >
> > It might be something like kallsyms_full.c and/or kallsyms_tiny.c.
> >
>
> This patch is not taken by Luis yet in module-tetsing branch.
Please resend that patch, as I'm happy to route it in through
modules-next [0]. I use modules-testing *prior* to pushing to
modules-next, if 0-day does not complain after about a few days
then I push to modules-next and this gets merged to linux-next.
You can send that patch and then this one and include in the subject
something like:
[PATCH modules-next 1/1]
Vimal, I'd like your review of these patches too. And after those
we can see where your change fits / if it is still needed.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=modules-next
Luis
next prev parent reply other threads:[~2022-04-20 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220413055318epcas5p3df3cdde54a559d4002a74de9f23289f2@epcas5p3.samsung.com>
2022-04-13 5:53 ` Maninder Singh
2022-04-13 9:24 ` Petr Mladek
[not found] ` <CGME20220413055318epcas5p3df3cdde54a559d4002a74de9f23289f2@epcms5p5>
2022-04-18 4:34 ` Maninder Singh
2022-04-20 11:00 ` Petr Mladek
2022-04-20 15:21 ` Luis Chamberlain [this message]
2022-04-27 12:31 ` Vimal Agrawal
[not found] ` <CGME20220413055318epcas5p3df3cdde54a559d4002a74de9f23289f2@epcms5p7>
2022-05-07 5:49 ` Maninder Singh
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=YmAlAvy6aSeeJKoO@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ast@kernel.org \
--cc=avimalin@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gary@garyguo.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=mbenes@suse.cz \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=onkarnath.1@samsung.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=swboyd@chromium.org \
--cc=v.narang@samsung.com \
--cc=void@manifault.com \
--cc=wangkefeng.wang@huawei.com \
--cc=wedsonaf@google.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
all inboxes | Powered by JetHome®