From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <cang@codeaurora.org>
Cc: subhashj@codeaurora.org, asutoshd@codeaurora.org,
vivek.gautam@codeaurora.org, rnayak@codeaurora.org,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
Gilad Broner <gbroner@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
Yaniv Gardi <ygardi@codeaurora.org>,
Sujit Reddy Thumma <sthumma@codeaurora.org>,
Amit Nischal <anischal@codeaurora.org>,
Maya Erez <merez@codeaurora.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scsi: ufs-qcom: add number of lanes for Tx and Rx links
Date: Tue, 27 Feb 2018 21:23:44 -0500 [thread overview]
Message-ID: <yq1sh9l4ztb.fsf@oracle.com> (raw)
In-Reply-To: <20180227055500.10416-1-cang@codeaurora.org> (Can Guo's message of "Tue, 27 Feb 2018 13:46:17 +0800")
Can,
> Different platforms may have different number of lanes for the UFS
> Tx/Rx links. Add parameter to device tree specifying how many lanes
> should be configured for the UFS Tx/Rx links. And don't print err
> message for clocks that are optional, this leads to unnecessary
> confusion about failure.
Does not apply to 4.17/scsi-queue. Please rebase and repost.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-02-28 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 5:46 [PATCH v2] scsi: ufs-qcom: add number of lanes for Tx and Rx links Can Guo
2018-02-28 2:23 ` Martin K. Petersen [this message]
2018-03-05 22:02 ` Rob Herring
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=yq1sh9l4ztb.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=anischal@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gbroner@codeaurora.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=merez@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sthumma@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=venkatg@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.org \
--cc=ygardi@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 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).