From: Christoph Hellwig <hch@lst.de>
To: "Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Gerd Bayer <gbayer@linux.ibm.com>,
"asahi@lists.linux.dev" <asahi@lists.linux.dev>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: max_hw_sectors error caused by recent NVMe driver commit
Date: Mon, 13 Feb 2023 07:42:50 +0100 [thread overview]
Message-ID: <20230213064250.GA14558@lst.de> (raw)
In-Reply-To: <BYAPR21MB1688F70E49AAD658D86C439DD7DD9@BYAPR21MB1688.namprd21.prod.outlook.com>
On Mon, Feb 13, 2023 at 06:41:12AM +0000, Michael Kelley (LINUX) wrote:
> Any reason to use dev->dev instead of &pdev->dev? They should be
> the same, but with everything else in this function using &pdev->dev,
> the lack of consistency suggests there might be a reason.
No good reason - the code started with copy and paste from the previous
location and I can fix this up.
prev parent reply other threads:[~2023-02-13 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 5:33 max_hw_sectors error caused by recent NVMe driver commit Michael Kelley (LINUX)
2023-02-11 9:38 ` Daniel Gomez
2023-02-13 16:42 ` Michael Kelley (LINUX)
2023-02-13 16:57 ` Keith Busch
2023-02-17 13:28 ` Daniel Gomez
2023-02-17 16:05 ` Michael Kelley (LINUX)
2023-03-03 16:24 ` Daniel Gomez
2023-03-03 16:44 ` Keith Busch
2023-02-13 5:59 ` Christoph Hellwig
2023-02-13 6:41 ` Michael Kelley (LINUX)
2023-02-13 6:42 ` Christoph Hellwig [this message]
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=20230213064250.GA14558@lst.de \
--to=hch@lst.de \
--cc=asahi@lists.linux.dev \
--cc=gbayer@linux.ibm.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mikelley@microsoft.com \
--cc=sagi@grimberg.me \
/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.