From: chunfeng.yun@mediatek.com (chunfeng yun)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] phy: phy-mt65xx-usb3: fix test fail of HS receiver sensitivity
Date: Tue, 17 Nov 2015 15:50:02 +0800 [thread overview]
Message-ID: <1447746602.18917.8.camel@mhfsdcap03> (raw)
In-Reply-To: <20151117061619.GB18947@kroah.com>
Hi,
On Mon, 2015-11-16 at 22:16 -0800, Greg KH wrote:
> On Tue, Nov 17, 2015 at 02:02:58PM +0800, Chunfeng Yun wrote:
> > when use the default value 8 of RG_USB20_SQTH, the HS receiver
> > sensitivity test of HQA will fail, set it as 2 to fix up the
> > issue.
> >
> > Change-Id: Ia5bdbbfc8ebb170d3ef26007e665b7350b6d28ab
>
> What is this field for? Hint, it should never be there for a patch you
> submit upstream as it means nothing...
>
I'm sorry for forgetting remove it.
And I will remove change-id in next round after review
Thanks a lot
> greg k-h
prev parent reply other threads:[~2015-11-17 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 6:02 [PATCH] phy: phy-mt65xx-usb3: fix test fail of HS receiver sensitivity Chunfeng Yun
2015-11-17 6:16 ` Greg KH
2015-11-17 7:50 ` chunfeng yun [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=1447746602.18917.8.camel@mhfsdcap03 \
--to=chunfeng.yun@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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