From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
ulf.hansson@linaro.org, cheol.yong.kim@intel.com,
linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
qi-ming.wu@intel.com, michal.simek@xilinx.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] mmc: sdhci-of-arasan: Add Support for Intel LGM SDXC
Date: Wed, 9 Oct 2019 17:47:51 +0800 [thread overview]
Message-ID: <00bb038f-f959-74bf-e598-45891e65d73e@linux.intel.com> (raw)
In-Reply-To: <20191009094005.GB32742@smile.fi.intel.com>
Hi Andy,
On 9/10/2019 5:40 PM, Andy Shevchenko wrote:
> On Wed, Oct 09, 2019 at 09:06:16AM +0800, Ramuthevar, Vadivel MuruganX wrote:
>> Hi Adrian,
>>
>> Thank you for the Acked-by, will add *Acked-by* in the next-patch.
> Please, stop top-posting.
>
> Besides that, there is no need for next version if the only comments you got
> are ACKs. Rb:s, etc.
Sure, Thanks!
---
Regards
Vadivel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-09 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 4:00 [PATCH v1 0/2] mmc: sdhci-of-arasan: Add Support for Intel LGM SDXC Ramuthevar, Vadivel MuruganX
2019-10-03 4:00 ` [PATCH v1 1/2] dt-bindings: mmc: sdhci-of-arasan: Add new compatible " Ramuthevar,Vadivel MuruganX
2019-10-03 4:00 ` [PATCH v1 2/2] mmc: sdhci-of-arasan: Add Support " Ramuthevar,Vadivel MuruganX
2019-10-03 7:02 ` Adrian Hunter
2019-10-03 7:46 ` Ramuthevar, Vadivel MuruganX
2019-10-07 7:33 ` Ramuthevar, Vadivel MuruganX
2019-10-08 13:44 ` Adrian Hunter
[not found] ` <38228535-8d4c-76e9-f568-c0dfdc3994b3@linux.intel.com>
2019-10-09 9:40 ` Andy Shevchenko
2019-10-09 9:47 ` Ramuthevar, Vadivel MuruganX [this message]
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=00bb038f-f959-74bf-e598-45891e65d73e@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=qi-ming.wu@intel.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/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).