Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   Jens Axboe <axboe@kernel.dk>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH 0/4] null_blk: fixes around nr_devices and log improvements
Date:   Fri, 13 Sep 2019 12:03:34 -0700
Message-Id: <FFDFD18F-C242-46D2-B64B-5515987AD82D@kernel.dk>
References: <20190913185746.337429-1-andrealmeid@collabora.com>
Cc:     linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org, corbet@lwn.net, kernel@collabora.com,
        krisman@collabora.com
In-Reply-To: <20190913185746.337429-1-andrealmeid@collabora.com>
To:     =?utf-8?Q?Andr=C3=A9_Almeida?= <andrealmeid@collabora.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sep 13, 2019, at 11:58 AM, Andr=C3=A9 Almeida <andrealmeid@collabora.com>=
 wrote:
>=20
> =EF=BB=BFHello,
>=20
> This patch series address feedback for a previous patch series sent by
> me "docs: block: null_blk: enhance document style"[1].
>=20
> First patch removes a restriction that prevents null_blk to load with
> (nr_devices =3D=3D 0). This restriction breaks applications, so it's a bug=
. I
> have tested it running the kernel with `null_blk.nr_devices=3D0`.
>=20
> 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.
>=20
> 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.

Please add Fixes tags to your patches.=20