From: Maninder Singh <maninder1.s@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "pmladek@suse.com" <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>,
"linux@rasmusvillemoes.dk" <linux@rasmusvillemoes.dk>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
Vaneet Narang <v.narang@samsung.com>,
"swboyd@chromium.org" <swboyd@chromium.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
"avimalin@gmail.com" <avimalin@gmail.com>,
"atomlin@redhat.com" <atomlin@redhat.com>
Subject: RE: [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
Date: Wed, 16 Mar 2022 10:09:53 +0530 [thread overview]
Message-ID: <453510261.3922147.1647405593710@mail-kr5-2> (raw)
In-Reply-To: <YjDScHjMUbqYV4s4@bombadil.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
Hi Luis,
>> ---
>> commit id 'kallsyms: print module name in %ps/S case when KALLSYMS is disabled'
>> needs to be removed from mm(linux-next) tree, current change is
>> with ignorance of this commit. I was not sure how to send patch, with 2 patches
>> consisting reversal commit also, or current approach is correct.
>>
>> v1->v2: hash base address of module, change *fmt to fmt[0] and removed
>> copy paste.
>> v2->v3: fixed review comments from Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>
>> include/linux/kallsyms.h | 2 +
>> include/linux/module.h | 20 ++++++++++
>> kernel/kallsyms.c | 27 +++++++------
>> kernel/module.c | 4 +-
>> lib/vsprintf.c | 85 ++++++++++++++++++++++++++++++++++------
>
> Hey Maninder, thanks for your patch!
>
> Since this touches kernel/module.c and include/linux/module.h I'd prefer
> this go through modules-next [0], and as you will see that's a different
> world right now. I also have a set of at least 2 other patch sets to
> merge there before yours.
>
> Also, what is on modules-next is not intended to go to Linus for the
> next merge window as the changes there got merged only late, and I want
> at least 2 months of testing on linux-newt before any pull requiest is
> sent to Linus.
>
> Can you rebase to modules-next? I can evaluate the patches then for
> integration there once the other stuff gets merged into that tree too.
>
> [0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=modules-next
>
> Luis
prepared and verified patch(KALLSYMS enabled and disabled both) on module-next rebase and sent in new mail.
[PATCH 1/1 module-next] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
https://lkml.org/lkml/2022/3/16/7
Thanks,
Maninder Singh
[-- Attachment #2: rcptInfo.txt --]
[-- Type: application/octet-stream, Size: 1664 bytes --]
=================================================================================================================================
Subject : Re: [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
From : null
Sent Date : 2022-03-15 23:23 GMT+5:30
=================================================================================================================================
Name Type Job Title Dept. Company
=================================================================================================================================
Maninder Singh TO Staff Engineer System S/W Group /SRI-Delhi Samsung Electronics
pmladek@suse.com CC
rostedt@goodmis.org CC
senozhatsky@chromium.org CC
andriy.shevchenko@linux.i... CC
linux@rasmusvillemoes.dk CC
akpm@linux-foundation.org CC
wangkefeng.wang@huawei.com CC
Vaneet Narang CC Associate Architect System S/W Group /SRI-Delhi Samsung Electronics
swboyd@chromium.org CC
ojeda@kernel.org CC
linux-kernel@vger.kernel.org CC
linux-modules@vger.kernel... CC
avimalin@gmail.com CC
atomlin@redhat.com CC
=================================================================================================================================
prev parent reply other threads:[~2022-03-16 4:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220315155109epcas5p249963f50d68ee368edb569b1a9e7d63c@epcas5p2.samsung.com>
2022-03-15 15:51 ` [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled Maninder Singh
2022-03-15 17:52 ` Luis Chamberlain
2022-03-16 6:40 ` Christophe Leroy
2022-03-16 8:25 ` Luis Chamberlain
2022-03-16 8:27 ` Luis Chamberlain
2022-03-21 13:39 ` Aaron Tomlin
2022-03-21 17:35 ` Luis Chamberlain
[not found] ` <CGME20220315155109epcas5p249963f50d68ee368edb569b1a9e7d63c@epcms5p1>
2022-03-16 9:01 ` Maninder Singh
[not found] ` <CGME20220315155109epcas5p249963f50d68ee368edb569b1a9e7d63c@epcms5p6>
2022-03-16 4:39 ` Maninder Singh [this message]
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=453510261.3922147.1647405593710@mail-kr5-2 \
--to=maninder1.s@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=atomlin@redhat.com \
--cc=avimalin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=swboyd@chromium.org \
--cc=v.narang@samsung.com \
--cc=wangkefeng.wang@huawei.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).