[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190913220300.422869-1-andrealmeid@collabora.com>
Date: Fri, 13 Sep 2019 19:02:56 -0300
From: André Almeida <andrealmeid@...labora.com>
To: linux-block@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: corbet@....net, axboe@...nel.dk, kernel@...labora.com,
krisman@...labora.com,
André Almeida <andrealmeid@...labora.com>
Subject: [PATCH v2 0/4] null_blk: fixes around nr_devices and log improvements
Hello,
This patch series address feedback for a previous patch series sent by
me "docs: block: null_blk: enhance document style"[1].
First patch removes a restriction that prevents null_blk to load with
(nr_devices == 0). This restriction breaks applications, so it's a bug. I
have tested it running the kernel with `null_blk.nr_devices=0`.
In the previous series I have changed the type of var nr_devices, but I
forgot to change the type at module_param(). The second patch fix that.
The third patch uses a cleaver approach to make log messages consistent
using pr_fmt and the last one add a note on how to do that at the
coding style documentation.
Thanks,
André
Changes since v1:
- Add "Fixes" tag at [2/4]
- No more headers reordering at [3/4]
- Use #undef pr_fmt and KBUILD_MODNAME at [3/4] and [4/4]
- Replace "printk.h" for "kernel.h" at [4/4]
More details are provided at each patch changelog
[1] https://patchwork.kernel.org/project/linux-block/list/?series=172853
André Almeida (4):
null_blk: do not fail the module load with zero devices
null_blk: match the type of parameter nr_devices
null_blk: format pr_* logs with pr_fmt
coding-style: add explanation about pr_fmt macro
Documentation/process/coding-style.rst | 10 +++++++++-
drivers/block/null_blk.h | 4 +++-
drivers/block/null_blk_main.c | 24 ++++++++++--------------
drivers/block/null_blk_zoned.c | 6 +++---
4 files changed, 25 insertions(+), 19 deletions(-)
--
2.23.0
Powered by blists - more mailing lists