[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1348328452.2521.78.camel@bwh-desktop.uk.solarflarecom.com>
Date: Sat, 22 Sep 2012 16:40:52 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Richard Cochran <richardcochran@...il.com>
CC: <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>,
Jacob Keller <jacob.e.keller@...el.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
John Stultz <john.stultz@...aro.org>,
Matthew Vick <matthew.vick@...el.com>
Subject: Re: [PATCH V2 net-next 3/4] ptp: link the phc device to its parent
device
On Sat, 2012-09-22 at 09:42 +0200, Richard Cochran wrote:
> PTP Hardware Clock devices appear as class devices in sysfs. This patch
> changes the registration API to use the parent device, clarifying the
> clock's relationship to the underlying device.
[...]
> --- a/drivers/net/ethernet/sfc/ptp.c
> +++ b/drivers/net/ethernet/sfc/ptp.c
> @@ -931,7 +931,8 @@ static int efx_ptp_probe_channel(struct efx_channel *channel)
> ptp->phc_clock_info.settime = efx_phc_settime;
> ptp->phc_clock_info.enable = efx_phc_enable;
>
> - ptp->phc_clock = ptp_clock_register(&ptp->phc_clock_info);
> + ptp->phc_clock = ptp_clock_register(&ptp->phc_clock_info,
> + &channel->napi_dev->dev);
[...]
channel->napi_dev is the net device, not the PCI device. The parent
device should be &efx->pci_dev->dev.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists