From: Matthew Wilcox <willy@infradead.org>
To: Anton Suvorov <warwish@yandex-team.ru>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dmtrmonakhov@yandex-team.ru, linux-block@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH 02/10] dax: reduce stack footprint dealing with block device names
Date: Wed, 2 Jun 2021 18:18:48 +0100 [thread overview]
Message-ID: <YLe9eDbG2c/rVjyu@casper.infradead.org> (raw)
In-Reply-To: <20210602152903.910190-3-warwish@yandex-team.ru>
On Wed, Jun 02, 2021 at 06:28:55PM +0300, Anton Suvorov wrote:
> @@ -81,29 +80,29 @@ bool __generic_fsdax_supported(struct dax_device *dax_dev,
> int err, id;
>
> if (blocksize != PAGE_SIZE) {
> - pr_info("%s: error: unsupported blocksize for dax\n",
> - bdevname(bdev, buf));
> + pr_info("%pg: error: unsupported blocksize for dax\n",
> + bdev);
You can combine these onto one line without passing 80 columns:
pr_info("%pg: error: unsupported blocksize for dax\n", bdev);
(many other examples of this)
next prev parent reply other threads:[~2021-06-02 17:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 15:28 [PATCH 00/10] reduce stack footprint printing bdev names Anton Suvorov
2021-06-02 15:28 ` [PATCH 01/10] drbd: reduce stack footprint in drbd_report_io_error() Anton Suvorov
2021-06-02 15:28 ` [PATCH 02/10] dax: reduce stack footprint dealing with block device names Anton Suvorov
2021-06-02 17:18 ` Matthew Wilcox [this message]
2021-06-22 17:44 ` [PATCH v2 00/10] reduce stack footprint printing bdev names Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 01/10] drbd: reduce stack footprint in drbd_report_io_error() Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 02/10] dax: reduce stack footprint dealing with block device names Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 03/10] raid-md: " Anton Suvorov
2021-06-23 8:26 ` Guoqing Jiang
2021-06-22 17:44 ` [PATCH v2 04/10] dm: " Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 05/10] block: " Anton Suvorov
2021-06-23 7:45 ` Christoph Hellwig
2021-06-22 17:44 ` [PATCH v2 06/10] target: reduce stack footprint in iblock_show_configfs_dev_params() Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 07/10] vfs: reduce stack footprint in __blkdev_put() Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 08/10] ext4: reduce stack footprint in ext4_end_bio() Anton Suvorov
2021-06-22 17:44 ` [PATCH v2 09/10] security: reduce stack footprint in loadpin_read_file() Anton Suvorov
2021-06-22 17:45 ` [PATCH v2 10/10] block: remove unused symbol bio_devname() Anton Suvorov
2021-06-02 15:28 ` [PATCH 03/10] raid-md: reduce stack footprint dealing with block device names Anton Suvorov
2021-06-02 15:28 ` [PATCH 04/10] dm: " Anton Suvorov
2021-06-23 20:20 ` Mike Snitzer
2021-06-02 15:28 ` [PATCH 05/10] block: " Anton Suvorov
2021-06-02 15:28 ` [PATCH 06/10] target: reduce stack footprint in iblock_show_configfs_dev_params() Anton Suvorov
2021-06-02 15:29 ` [PATCH 07/10] vfs: reduce stack footprint in __blkdev_put() Anton Suvorov
2021-06-02 15:29 ` [PATCH 08/10] ext4: reduce stack footprint in ext4_end_bio() Anton Suvorov
2021-06-02 15:29 ` [PATCH 09/10] security: reduce stack footprint in loadpin_read_file() Anton Suvorov
2021-06-02 15:29 ` [PATCH 10/10] block: remove unused symbol bio_devname() Anton Suvorov
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=YLe9eDbG2c/rVjyu@casper.infradead.org \
--to=willy@infradead.org \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=warwish@yandex-team.ru \
/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).