From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kishon@ti.com, cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
peter.harliman.liem@intel.com, Ramuthevar@smile.fi.intel.com
Subject: Re: [PATCH v7 2/2] phy: intel-lgm-emmc: Add support for eMMC PHY
Date: Wed, 11 Dec 2019 10:44:35 +0800 [thread overview]
Message-ID: <6dac436f-956f-534e-7e15-7aa2f0881217@linux.intel.com> (raw)
In-Reply-To: <20191210135450.GX32742@smile.fi.intel.com>
Hi,
On 10/12/2019 9:54 PM, Andy Shevchenko wrote:
> On Tue, Dec 10, 2019 at 10:53:01AM +0800, Ramuthevar,Vadivel MuruganX wrote:
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> Add support for eMMC PHY on Intel's Lightning Mountain SoC.
>> Signed-off-by: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>> Signed-off-by: Ramuthevar,Vadivel MuruganX <vadivel.muruganx.ramuthevar@linux.intel.com>
> Something wrong with the second SoB. And why you have two to begin with?
Thanks Andy, Good catch, I will correct it and send patch again.
Best Regards
vadivel
next prev parent reply other threads:[~2019-12-11 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 2:52 [PATCH v7 0/2] phy: intel-lgm-emmc: Add support for eMMC PHY Ramuthevar,Vadivel MuruganX
2019-12-10 2:53 ` [PATCH v7 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM " Ramuthevar,Vadivel MuruganX
2019-12-10 2:53 ` [PATCH v7 2/2] phy: intel-lgm-emmc: Add support for " Ramuthevar,Vadivel MuruganX
2019-12-10 13:54 ` Andy Shevchenko
2019-12-11 2:44 ` Ramuthevar, Vadivel MuruganX [this message]
2019-12-11 2:50 [PATCH v7 0/2] " Ramuthevar,Vadivel MuruganX
2019-12-11 2:50 ` [PATCH v7 2/2] " Ramuthevar,Vadivel MuruganX
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=6dac436f-956f-534e-7e15-7aa2f0881217@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=Ramuthevar@smile.fi.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.harliman.liem@intel.com \
--cc=qi-ming.wu@intel.com \
/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).