linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Enric Balletbo Serra <eballetbo@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Guenter Roeck <groeck@google.com>,
	kieran.bingham@ideasonboard.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	kernel@collabora.com, Benson Leung <bleung@chromium.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] phy: phy-rockchip-inno-usb2: drop reading the utmi-avalid property
Date: Wed, 16 Jan 2019 11:04:28 +0100	[thread overview]
Message-ID: <CAFqH_52gy8oUUAy61O+gMycd08Q22ZS1mqh6fm6TXzKfO1CgyQ@mail.gmail.com> (raw)
In-Reply-To: <8a0ea28a-961f-130b-bd76-9dbda42ea417@ti.com>

Hi,

Missatge de Kishon Vijay Abraham I <kishon@ti.com> del dia dc., 16 de
gen. 2019 a les 9:46:
>
> Hi,
>
> On 10/01/19 5:56 PM, Heiko Stuebner wrote:
> > Am Mittwoch, 9. Januar 2019, 18:14:15 CET schrieb Enric Balletbo i Serra:
> >> That property is no used in mainline and is not documented. The only
> >> board using that property is the rk33-99-evb-rev1 and -rev2 in the
> >> vendor kernel. The existence of a further -rev3 (which also looks way
> >> better cared for compared rev1+2) indicates that the older ones are
> >> probably some sort of preproduction models, where some wiring (on the soc
> >> or board) may have gone wrong.
> >>
> >> It is also not clear why this is a hardware-description or a DT
> >> property, so, as noboby seems to care of this just drop reading that
> >> property.
> >>
> >> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> >
> > Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>
> For some reason, I don't seem to have the original patch in the inbox. Can you
> resend it please?
>
Yes, seems that for some reason my script to add the maintainers
failed, sorry about that. I'll resend the last three patches.

> Thanks
> Kishon
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-01-16 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 17:14 [PATCH v2] phy: phy-rockchip-inno-usb2: drop reading the utmi-avalid property Enric Balletbo i Serra
2019-01-10 12:26 ` Heiko Stuebner
2019-01-16  8:45   ` Kishon Vijay Abraham I
2019-01-16 10:04     ` Enric Balletbo Serra [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=CAFqH_52gy8oUUAy61O+gMycd08Q22ZS1mqh6fm6TXzKfO1CgyQ@mail.gmail.com \
    --to=eballetbo@gmail.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@google.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@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;
as well as URLs for NNTP newsgroup(s).