From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH] nvme-pci: Use dev_get_drvdata where possible
Date: Thu, 25 Jul 2019 22:14:22 +0900 [thread overview]
Message-ID: <20190725131422.GA7289@minwoo-desktop> (raw)
In-Reply-To: <20190724122235.21639-1-hslester96@gmail.com>
On 19-07-24 20:22:35, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan <hslester96 at gmail.com>
This looks good to me.
Reviewed-by: Minwoo Im <minwoo.im.dev at gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Jens Axboe <axboe@fb.com>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Minwoo Im <minwoo.im.dev@gmail.com>
Subject: Re: [PATCH] nvme-pci: Use dev_get_drvdata where possible
Date: Thu, 25 Jul 2019 22:14:22 +0900 [thread overview]
Message-ID: <20190725131422.GA7289@minwoo-desktop> (raw)
In-Reply-To: <20190724122235.21639-1-hslester96@gmail.com>
On 19-07-24 20:22:35, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
This looks good to me.
Reviewed-by: Minwoo Im <minwoo.im.dev@gmail.com>
next prev parent reply other threads:[~2019-07-25 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 12:22 [PATCH] nvme-pci: Use dev_get_drvdata where possible Chuhong Yuan
2019-07-24 12:22 ` Chuhong Yuan
2019-07-24 18:15 ` Sagi Grimberg
2019-07-24 18:15 ` Sagi Grimberg
2019-07-25 13:14 ` Minwoo Im [this message]
2019-07-25 13:14 ` Minwoo Im
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=20190725131422.GA7289@minwoo-desktop \
--to=minwoo.im.dev@gmail.com \
/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.