From: David Miller <davem@davemloft.net>
To: ddaney@caviumnetworks.com
Cc: ddaney.cavm@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, f.fainelli@gmail.com,
netdev@vger.kernel.org, david.daney@cavium.com
Subject: Re: [PATCH] net: mdio-octeon: Add PCI driver binding.
Date: Thu, 24 Sep 2015 16:07:57 -0700 (PDT) [thread overview]
Message-ID: <20150924.160757.907239258265499481.davem@davemloft.net> (raw)
In-Reply-To: <56047F26.9070305@caviumnetworks.com>
From: David Daney <ddaney@caviumnetworks.com>
Date: Thu, 24 Sep 2015 15:54:30 -0700
> On 09/24/2015 03:50 PM, David Miller wrote:
>> From: David Daney <ddaney@caviumnetworks.com>
>> Date: Thu, 24 Sep 2015 15:45:41 -0700
>>
>>> 2) The OF device tree nodes for PCI devices do not result in the
>>> creation of a platform device.
>>
>> But they are created for the children right? And that's the one
>> you need them for probing.
>>
>> I'm still not convinced, sorry.
>>
>
> Let's let this topic rest for a few days. My original patch was
> defective, so it cannot be merged. I will sleep on this, try a few
> things and perhaps revisit it if I still think it is advisable.
Ok.
prev parent reply other threads:[~2015-09-24 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 0:41 [PATCH] net: mdio-octeon: Add PCI driver binding David Daney
[not found] ` <1442968896-30776-1-git-send-email-ddaney.cavm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-24 21:52 ` David Miller
2015-09-24 22:04 ` David Daney
[not found] ` <56047367.3060101-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2015-09-24 22:12 ` David Daney
2015-09-24 22:16 ` David Miller
2015-09-24 22:14 ` David Miller
[not found] ` <20150924.151451.1059470233561232912.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2015-09-24 22:45 ` David Daney
2015-09-24 22:50 ` David Miller
2015-09-24 22:54 ` David Daney
2015-09-24 23:07 ` David Miller [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=20150924.160757.907239258265499481.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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 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).