From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
kbusch@kernel.org
Subject: Re: [PATCH] nvme-core: check bdev value for NULL
Date: Wed, 27 Jan 2021 10:09:19 -0700 [thread overview]
Message-ID: <683a593e-a5f2-0e09-2ad1-c2527946b253@kernel.dk> (raw)
In-Reply-To: <20210127071344.GA21223@lst.de>
On 1/27/21 12:13 AM, Christoph Hellwig wrote:
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Jens, can you pick this up as it fixes an issue I introduced in
> for-5.12/block?
I can, I'll add the fixes tag too.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-block@vger.kernel.org, kbusch@kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-core: check bdev value for NULL
Date: Wed, 27 Jan 2021 10:09:19 -0700 [thread overview]
Message-ID: <683a593e-a5f2-0e09-2ad1-c2527946b253@kernel.dk> (raw)
In-Reply-To: <20210127071344.GA21223@lst.de>
On 1/27/21 12:13 AM, Christoph Hellwig wrote:
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Jens, can you pick this up as it fixes an issue I introduced in
> for-5.12/block?
I can, I'll add the fixes tag too.
--
Jens Axboe
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-27 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 5:37 [PATCH] nvme-core: check bdev value for NULL Chaitanya Kulkarni
2021-01-27 5:37 ` Chaitanya Kulkarni
2021-01-27 7:13 ` Christoph Hellwig
2021-01-27 7:13 ` Christoph Hellwig
2021-01-27 17:09 ` Jens Axboe [this message]
2021-01-27 17:09 ` Jens Axboe
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=683a593e-a5f2-0e09-2ad1-c2527946b253@kernel.dk \
--to=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.