From: Luis Chamberlain <mcgrof@bombadil.infradead.org>
To: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
jim.cromie@gmail.com
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH 0/4] cosmetic fixes to module pr_debugs
Date: Wed, 22 Mar 2023 16:38:59 -0700 [thread overview]
Message-ID: <167952830755.2267106.14602423112302281916.b4-ty@kernel.org> (raw)
In-Reply-To: <20230322013623.251401-1-jim.cromie@gmail.com>
From: Luis Chamberlain <mcgrof@kernel.org>
On Tue, 21 Mar 2023 19:36:19 -0600, Jim Cromie wrote:
> These 4 patches alter pr_debug() messages for more info, and less
> log-spam.
>
> * add "for $modname:" to banners
> helpful for finding one of many
>
> [ 40.885922] main:layout_sections: Core section allocation order for test_dynamic_debug:
> ~20 lines of output
> [ 40.885967] main:move_module: Final section addresses for test_dynamic_debug:
> ~2 lines - .init.text/data
>
> [...]
Applied, thanks!
[1/4] module: in layout_sections, move_module: add the modname
commit: 4ab9c7dca82f215fa596fb61192384e4c922bf9c
[2/4] module: add symbol-name to pr_debug Absolute symbol
commit: 9f5d69a7852db158bc9f5c5afa105ce12058afc3
[3/4] module: add section-size to move_module pr_debug
commit: 8cf2cfac04e4b24dfc4371306e202b09ab574a80
[4/4] module: already_uses() - reduce pr_debug output volume
commit: 6e82310365bade624ff38dd11a8467739adab6cc
Luis
prev parent reply other threads:[~2023-03-22 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 1:36 Jim Cromie
2023-03-22 1:36 ` [PATCH 1/4] module: in layout_sections, move_module: add the modname Jim Cromie
2023-03-22 1:36 ` [PATCH 2/4] module: add symbol-name to pr_debug Absolute symbol Jim Cromie
2023-03-22 1:36 ` [PATCH 3/4] module: add section-size to move_module pr_debug Jim Cromie
2023-03-22 1:36 ` [PATCH 4/4] module: already_uses() - reduce pr_debug output volume Jim Cromie
2023-03-22 23:38 ` Luis Chamberlain [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=167952830755.2267106.14602423112302281916.b4-ty@kernel.org \
--to=mcgrof@bombadil.infradead.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
/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®