From: Aaron Tomlin <atomlin@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Michal Suchánek" <msuchanek@suse.de>,
"Maninder Singh" <maninder1.s@samsung.com>,
"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>,
"v.narang@samsung.com" <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>
Subject: Re: [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
Date: Mon, 21 Mar 2022 13:39:42 +0000 [thread overview]
Message-ID: <20220321133942.pbv7vvkn5r62ky5x@ava.usersys.com> (raw)
In-Reply-To: <YjGe961XL8GW7Qeh@bombadil.infradead.org>
On Wed 2022-03-16 01:25 -0700, Luis Chamberlain wrote:
> I know this has been quite a bit of churn, but given Aaron's series I
> really hope we're goint to be in a better place for maintenance for
> modules long term.
>
> I guess I gotta go automate tests to these things somehow too.
Hi Luis,
I can send a v12 now if you'd like?
Kind regards,
--
Aaron Tomlin
next prev parent reply other threads:[~2022-03-21 13:39 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 4:39 ` Maninder Singh
2022-03-16 6:40 ` Christophe Leroy
2022-03-16 8:25 ` Luis Chamberlain
2022-03-16 8:27 ` Luis Chamberlain
2022-03-16 9:01 ` Maninder Singh
2022-03-21 13:39 ` Aaron Tomlin [this message]
2022-03-21 17:35 ` Luis Chamberlain
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=20220321133942.pbv7vvkn5r62ky5x@ava.usersys.com \
--to=atomlin@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avimalin@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maninder1.s@samsung.com \
--cc=mcgrof@kernel.org \
--cc=msuchanek@suse.de \
--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