From: Vignesh Raghavendra <vigneshr@ti.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, <jejb@linux.ibm.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Janek Kotas <jank@cadence.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<nsekhar@ti.com>
Subject: Re: [PATCH 0/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP
Date: Tue, 1 Oct 2019 13:38:46 +0530 [thread overview]
Message-ID: <bfcdfce5-64d5-4cd1-cefd-b363e6fddcd5@ti.com> (raw)
In-Reply-To: <yq14l0tw21j.fsf@oracle.com>
On 01/10/19 9:27 AM, Martin K. Petersen wrote:
>
> Vignesh,
>
>> This series add DT bindings and driver for TI wrapper for Cadence UFS
>> IP that is present on TI's J721e SoC
>
> Will need some reviews from DT and ufs folks respectively before I can
> queue this up.
>
Ok, thanks for the update! I guess I have the required reviewers on CC
for DT and SCSI/UFS as mentioned in MAINTAINERS file for . Please let me
know if I missed someone
Will wait for their comments/Acks.
> Thanks!
>
--
Regards
Vignesh
prev parent reply other threads:[~2019-10-01 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:39 [PATCH 0/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP Vignesh Raghavendra
2019-09-18 13:39 ` [PATCH 1/2] dt-bindings: ufs: ti,j721e-ufs.yaml: Add binding for TI UFS wrapper Vignesh Raghavendra
2019-10-01 12:08 ` Rob Herring
2019-10-01 12:18 ` Vignesh Raghavendra
2019-10-03 21:56 ` Rob Herring
2019-09-18 13:39 ` [PATCH 2/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP Vignesh Raghavendra
2019-10-01 3:57 ` [PATCH 0/2] " Martin K. Petersen
2019-10-01 8:08 ` Vignesh Raghavendra [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=bfcdfce5-64d5-4cd1-cefd-b363e6fddcd5@ti.com \
--to=vigneshr@ti.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=jank@cadence.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=nsekhar@ti.com \
--cc=pedrom.sousa@synopsys.com \
--cc=robh+dt@kernel.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).