From: Nikolay Borisov <nborisov@suse.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Remove noinline attribute from wait_for_commit
Date: Tue, 24 Nov 2020 17:42:57 +0200 [thread overview]
Message-ID: <ed0b6532-e4ee-1bdb-6376-0393c3d976b2@suse.com> (raw)
In-Reply-To: <20201124153950.GA1803@twin.jikos.cz>
On 24.11.20 г. 17:39 ч., David Sterba wrote:
> On Tue, Nov 24, 2020 at 04:45:02PM +0200, Nikolay Borisov wrote:
>> The function is a plain wrapper that noinline makes no sense.
>
> Or it is a way to let the function name appear in a stack trace, which
> could be useful for debugging or analyzing system state.
>
Well, this information could generally be derived by having the debug
info either in crash or one of the "beautify" scripts. In any case I
won't insist.
next prev parent reply other threads:[~2020-11-24 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:45 [PATCH] btrfs: Remove noinline attribute from wait_for_commit Nikolay Borisov
2020-11-24 15:39 ` David Sterba
2020-11-24 15:42 ` Nikolay Borisov [this message]
2020-11-24 16:05 ` David Sterba
2020-11-25 11:51 ` David Sterba
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=ed0b6532-e4ee-1bdb-6376-0393c3d976b2@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.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