On 6/4/18 10:40 AM, kvi...@gmail.com wrote:
> From: Kevin Vigor
>
> Existing dev_dbg messages sometimes identify request using request
> pointer, sometimes using nbd_cmd pointer. This makes it hard to
> follow request flow. Consistently use request pointer instead.
Applied, with the SOB added.
On 6/5/18 8:30 AM, Josef Bacik wrote:
> On Tue, Jun 05, 2018 at 08:23:06AM -0600, Jens Axboe wrote:
>> On 6/4/18 10:40 AM, kvi...@gmail.com wrote:
>>> From: Kevin Vigor
>>>
>>> Existing dev_dbg messages sometimes identify request using request
>>> pointer, sometimes using nbd_cmd pointer. This mak
On Tue, Jun 05, 2018 at 08:23:06AM -0600, Jens Axboe wrote:
> On 6/4/18 10:40 AM, kvi...@gmail.com wrote:
> > From: Kevin Vigor
> >
> > Existing dev_dbg messages sometimes identify request using request
> > pointer, sometimes using nbd_cmd pointer. This makes it hard to
> > follow request flow. C
On 6/4/18 10:40 AM, kvi...@gmail.com wrote:
> From: Kevin Vigor
>
> Existing dev_dbg messages sometimes identify request using request
> pointer, sometimes using nbd_cmd pointer. This makes it hard to
> follow request flow. Consistently use request pointer instead.
You're missing the Signed-off-
On Mon, Jun 04, 2018 at 10:40:12AM -0600, kvi...@gmail.com wrote:
> From: Kevin Vigor
>
> Existing dev_dbg messages sometimes identify request using request
> pointer, sometimes using nbd_cmd pointer. This makes it hard to
> follow request flow. Consistently use request pointer instead.
Reviewed
From: Kevin Vigor
Existing dev_dbg messages sometimes identify request using request
pointer, sometimes using nbd_cmd pointer. This makes it hard to
follow request flow. Consistently use request pointer instead.
---
drivers/block/nbd.c | 10 +-
1 file changed, 5 insertions(+), 5 deletion
