From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
kishon <kishon@ti.com>,
Vinayak Holikatti <vinholikatti@gmail.com>,
jejb@linux.vnet.ibm.com, open list <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org,
Subhash Jadavani <subhashj@codeaurora.org>,
evgreen@chromium.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH 2/3] scsi/ufs: qcom: Remove ufs_qcom_phy_*() calls from host
Date: Tue, 25 Sep 2018 20:28:20 -0400 [thread overview]
Message-ID: <yq1efdhhzkr.fsf@oracle.com> (raw)
In-Reply-To: <CAFp+6iFPOGRAToBrV44VDNYG4DP2c6_+8QZbKsDmM4SF57NGfQ@mail.gmail.com> (Vivek Gautam's message of "Tue, 25 Sep 2018 15:22:38 +0530")
Vivek,
> Kishon is looking to pick this series through linux-phy tree.
> Will you please consider giving your ack for this patch? Thanks.
Looks fine.
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-26 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:17 [PATCH 0/3] scsi: ufs-qcom: Remove all direct calls to qcom-ufs phy Vivek Gautam
2018-09-04 10:17 ` [PATCH 1/3] phy: qcom-ufs: Remove stale methods that handle ref clk Vivek Gautam
2018-09-24 17:23 ` Bjorn Andersson
2018-09-25 5:40 ` Vivek Gautam
2018-09-04 10:17 ` [PATCH 2/3] scsi/ufs: qcom: Remove ufs_qcom_phy_*() calls from host Vivek Gautam
2018-09-24 17:24 ` Bjorn Andersson
2018-09-25 9:52 ` Vivek Gautam
2018-09-26 0:28 ` Martin K. Petersen [this message]
2018-09-26 6:14 ` Vivek Gautam
2018-09-04 10:17 ` [PATCH 3/3] phy: qcom-ufs: Declare 20nm qcom ufs qmp phy as Broken Vivek Gautam
2018-09-24 17:29 ` Bjorn Andersson
2018-09-24 8:14 ` [PATCH 0/3] scsi: ufs-qcom: Remove all direct calls to qcom-ufs phy Vivek Gautam
2018-09-25 6:42 ` Kishon Vijay Abraham I
2018-09-25 6:42 ` Kishon Vijay Abraham I
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=yq1efdhhzkr.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.