From: Jason Gunthorpe <jgg@ziepe.ca>
To: Parav Pandit <parav@mellanox.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Dave Ertman <david.m.ertman@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
Kiran Patil <kiran.patil@intel.com>
Subject: Re: [net-next 1/1] virtual-bus: Implementation of Virtual Bus
Date: Tue, 12 Nov 2019 21:10:38 -0400 [thread overview]
Message-ID: <20191113011038.GC19615@ziepe.ca> (raw)
In-Reply-To: <AM0PR05MB48662DEDDE4750D399B8181ED1760@AM0PR05MB4866.eurprd05.prod.outlook.com>
On Wed, Nov 13, 2019 at 01:03:44AM +0000, Parav Pandit wrote:
> A small improvement below, because get_drvdata() and set_drvdata()
Here it was called 'devdata' not the existing drvdata - so something
different, I was confused for a bit too..
> is supposed to be called by the bus driver, not its creator. And
> below data structure achieve strong type checks, no void* casts, and
> exactly achieves the foo_device example. Isn't it better?
> mlx5_virtbus_device {
> struct virtbus_device dev;
> struct mlx5_core_dev *dev;
> };
This does seem a bit cleaner than using the void * trick (more, OOPy
at least)
Jason
next prev parent reply other threads:[~2019-11-13 1:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:22 [net-next 1/1] virtual-bus: Implementation of Virtual Bus Jeff Kirsher
2019-11-12 20:59 ` Jason Gunthorpe
2019-11-12 21:18 ` Ertman, David M
2019-11-12 21:28 ` Greg KH
2019-11-13 0:08 ` Jason Gunthorpe
2019-11-13 1:03 ` Parav Pandit
2019-11-13 1:10 ` Jason Gunthorpe [this message]
2019-11-13 6:44 ` Parav Pandit
2019-11-13 1:09 ` Ertman, David M
2019-11-13 7:03 ` Parav Pandit
2019-11-15 21:17 ` Ertman, David M
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=20191113011038.GC19615@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kiran.patil@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=parav@mellanox.com \
--cc=sassmann@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).