From: Jason Gunthorpe <jgg@nvidia.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v5] dmaengine: idxd: Do not use devm for 'struct device' object allocation
Date: Fri, 26 Mar 2021 20:55:32 -0300 [thread overview]
Message-ID: <20210326235532.GV2356281@nvidia.com> (raw)
In-Reply-To: <CAPcyv4gwqkzOHQ-xJ2At0Rc2k_S1X43XB607k8f-Djf7T-O3eQ@mail.gmail.com>
On Thu, Mar 25, 2021 at 11:02:46AM -0700, Dan Williams wrote:
> ...but aux-bus may need to contend with namespace collisions across
> users, so that's why the modname prefix is forced in device names.
> Also how would aux-drivers differentiate what they attach to with a
> single bus provided name?
Oh right, because the name comes from the bus, makes sense
Jason
next prev parent reply other threads:[~2021-03-26 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 14:56 [PATCH v5] dmaengine: idxd: Do not use devm for 'struct device' object allocation Dave Jiang
2021-03-04 18:03 ` Jason Gunthorpe
2021-03-04 18:20 ` Dave Jiang
2021-03-24 5:07 ` Dan Williams
2021-03-24 11:56 ` Jason Gunthorpe
2021-03-24 16:13 ` Dan Williams
2021-03-24 16:52 ` Jason Gunthorpe
2021-03-24 17:01 ` Dan Williams
2021-03-24 19:57 ` Dan Carpenter
2021-03-24 20:00 ` Dan Williams
2021-03-25 16:48 ` Jason Gunthorpe
2021-03-25 18:02 ` Dan Williams
2021-03-26 23:55 ` Jason Gunthorpe [this message]
2021-03-24 20:07 ` Dan Carpenter
2021-03-24 19:52 ` Dan Carpenter
2021-03-24 20:31 ` Dave Jiang
2021-03-24 23:35 ` Jason Gunthorpe
2021-03-25 6:52 ` Dan Carpenter
2021-03-25 11:45 ` Jason Gunthorpe
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=20210326235532.GV2356281@nvidia.com \
--to=jgg@nvidia.com \
--cc=dan.carpenter@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=vkoul@kernel.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.