From: Jessica Yu <jeyu@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Eugene Loh <eugene.loh@oracle.com>,
corbet@lwn.net, yamada.masahiro@socionext.com,
michal.lkml@markovi.net, linux-kbuild@vger.kernel.org,
maz@kernel.org, songliubraving@fb.com, tglx@linutronix.de,
jacob.e.keller@intel.com,
Kris Van Hees <kris.van.hees@oracle.com>,
Nick Alcock <nick.alcock@oracle.com>
Subject: Re: [PATCH v4] kallsyms: add names of built-in modules
Date: Thu, 19 Dec 2019 10:43:17 +0100 [thread overview]
Message-ID: <20191219094317.GA15318@linux-8ccs> (raw)
In-Reply-To: <20191218222931.76131c6a@rorschach.local.home>
+++ Steven Rostedt [18/12/19 22:29 -0500]:
>On Wed, 18 Dec 2019 15:55:18 -0800
>Eugene Loh <eugene.loh@oracle.com> wrote:
>
>> Ping.
>
>Couple of notes:
>
>1) this affects code that doesn't really have a maintainer. I could
>take it in my tree, but I would like to have acks from other
>maintainers. Perhaps Jessica Yu (Module maintainer), and probably one
>from Linus himself.
I hardly look through scripts/, so this patch would definitely need
Masahiro's (for all things kbuild) ack as well.
>2) Do not send new versions of a patch as a reply to the old version. I
>and many other maintainers sort our inbox by threads, and I look at the
>top of the thread for patches. That is, if there's another version of a
>patch that is a reply to a previous version, it is basically off my
>radar, unless I happen to notice it by chance (which I did with this
>email).
>
>You can send your v4 patch again, but please send it as its own thread,
>that way it will be on the radar of other maintainers. Hopefully we can
>get some acks on this as well.
Also, why wasn't this patch sent to lkml? At least I don't see it on
cc. If you resend v4, please send it there as well so it can get more
coverage.
Thanks,
Jessica
next prev parent reply other threads:[~2019-12-19 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 22:30 [PATCH] kallsyms: new /proc/kallmodsyms with builtin modules and symbol sizes eugene.loh
2019-11-15 16:47 ` Steven Rostedt
2019-11-15 17:26 ` Linus Torvalds
2019-11-16 17:58 ` Eugene Loh
2019-11-17 0:32 ` Linus Torvalds
2019-11-19 22:42 ` [PATCH v2] kallsyms: add names of built-in modules eugene.loh
2019-11-20 4:59 ` [PATCH v3] " eugene.loh
2019-11-22 10:00 ` Masahiro Yamada
2019-11-22 15:23 ` Nick Alcock
2019-11-22 17:04 ` Eugene Loh
2019-12-10 17:45 ` Eugene Loh
2019-12-10 17:48 ` [PATCH v4] " eugene.loh
2019-12-18 23:55 ` Eugene Loh
2019-12-19 3:29 ` Steven Rostedt
2019-12-19 4:28 ` Masahiro Yamada
2019-12-19 10:22 ` Masahiro Yamada
2020-01-08 18:32 ` Eugene Loh
2020-01-20 6:37 ` Masahiro Yamada
2020-01-24 18:08 ` Eugene Loh
2019-12-19 9:43 ` Jessica Yu [this message]
2019-11-20 0:11 ` [PATCH] kallsyms: new /proc/kallmodsyms with builtin modules and symbol sizes Eugene Loh
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=20191219094317.GA15318@linux-8ccs \
--to=jeyu@kernel.org \
--cc=corbet@lwn.net \
--cc=eugene.loh@oracle.com \
--cc=jacob.e.keller@intel.com \
--cc=kris.van.hees@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nick.alcock@oracle.com \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--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