From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Alim Akhtar" <alim.akhtar@samsung.com>
Cc: "'kernel test robot'" <lkp@intel.com>, <llvm@lists.linux.dev>,
<kbuild-all@lists.01.org>, <linux-kernel@vger.kernel.org>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>,
"'Chanho Park'" <chanho61.park@samsung.com>,
"'Bharat Uppal'" <bharat.uppal@samsung.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'?
Date: Mon, 13 Jun 2022 21:45:22 -0400 [thread overview]
Message-ID: <yq1mtegt3ym.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <000001d87e12$c6962770$53c27650$@samsung.com> (Alim Akhtar's message of "Sun, 12 Jun 2022 09:43:29 +0530")
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.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-06-14 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220611233355epcas5p1970bae9647eae17e20d330775b584695@epcas5p1.samsung.com>
2022-06-11 23:33 ` [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'? kernel test robot
2022-06-12 4:13 ` Alim Akhtar
2022-06-14 1:45 ` Martin K. Petersen [this message]
2022-06-14 1:49 ` Martin K. Petersen
2022-06-14 1:53 ` Alim Akhtar
2022-06-14 1:56 ` Martin K. Petersen
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=yq1mtegt3ym.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=bharat.uppal@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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).