linux-kernel - RE: [mkp-scsi:for-next 31/41] drivers/phy/samsung/phy-fsd-ufs.c:50:3: error: field designator 'cfgs' does not refer to any field in type 'const struct samsung_ufs_phy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <02b601d87f91$8bce05b0$a36a1110$@samsung.com>
Date:   Tue, 14 Jun 2022 07:23:27 +0530
From:   "Alim Akhtar" <alim.akhtar@...sung.com>
To:     "'Martin K. Petersen'" <martin.petersen@...cle.com>
Cc:     "'kernel test robot'" <lkp@...el.com>, <llvm@...ts.linux.dev>,
        <kbuild-all@...ts.01.org>, <linux-kernel@...r.kernel.org>,
        "'Chanho Park'" <chanho61.park@...sung.com>,
        "'Bharat Uppal'" <bharat.uppal@...sung.com>
Subject: RE: [mkp-scsi:for-next 31/41]
 drivers/phy/samsung/phy-fsd-ufs.c:50:3: error: field designator 'cfgs' does
 not refer to any field in type 'const struct samsung_ufs_phy_drvdata'; did
 you mean 'cfg'?

Hi Martin

>-----Original Message-----
>From: Martin K. Petersen [mailto:martin.petersen@...cle.com]
>Sent: Tuesday, June 14, 2022 7:15 AM
>To: Alim Akhtar <alim.akhtar@...sung.com>
>Cc: 'kernel test robot' <lkp@...el.com>; llvm@...ts.linux.dev; kbuild-
>all@...ts.01.org; linux-kernel@...r.kernel.org; 'Martin K. Petersen'
><martin.petersen@...cle.com>; 'Chanho Park'
><chanho61.park@...sung.com>; 'Bharat Uppal'
><bharat.uppal@...sung.com>
>Subject: Re: [mkp-scsi:for-next 31/41] drivers/phy/samsung/phy-fsd-
>ufs.c:50:3: error: field designator 'cfgs' does not refer to any field in
type
>'const struct samsung_ufs_phy_drvdata'; did you mean 'cfg'?
>
>
>Alim,
>
>> I was expecting phy driver changes will go via phy tree, where [1] is
>> available.
>>
>> @Martin, can you please take a look?
>>
>> You can just take the ufs changes (along with its device tree) and
>> drop the phy change or take the [1] above.
>
>Doesn't matter to me, happy to drop the series again. I just queued it up
to
>see if there would be any warnings.
>
No need to drop entire series, as UFS changes has got all Reviewed-by tags.

Just drop patch-{1/6, 2/6 and 3/6} (phy changes)

And please keep patch-{4/6, 5/6 and 6/6} in your tree

Thanks 

>--
>Martin K. Petersen	Oracle Linux Engineering