[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a03iCKbv6MZ0VZgZ21kP2+NHDBTXARAtGa-iPgLn1J2hg@mail.gmail.com>
Date: Mon, 29 May 2017 13:22:55 +0200
From: Arnd Bergmann <arnd@...db.de>
To: John Garry <john.garry@...wei.com>
Cc: "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
John Garry <john.garry2@...l.dcu.ie>, linuxarm@...wei.com,
linux-scsi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/22] scsi: hisi_sas: create hisi_sas_get_fw_info()
On Mon, May 29, 2017 at 1:18 PM, John Garry <john.garry@...wei.com> wrote:
> On 29/05/2017 11:53, Arnd Bergmann wrote:
>> On Thu, May 25, 2017 at 2:04 PM, John Garry <john.garry@...wei.com> wrote:
>
> So we only require these properties for platform device with DT firmware.
> This code is same as before (apart from adding the comments), but I'll
> consider adding a verbose comment.
>
> As for the check, effectively I already have what you recommend in how np is
> evaluated:
> + struct platform_device *pdev = hisi_hba->platform_dev;
> + struct device_node *np = pdev ? pdev->dev.of_node : NULL;
> struct clk *refclk;
Ah, very good. Thanks for checking.
Arnd
Powered by blists - more mailing lists