All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: t-kristo@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] ARM: OMAP5: add support for fref-xtal-clk
Date: Tue, 20 Mar 2018 08:09:11 -0700	[thread overview]
Message-ID: <20180320150911.GA5799@atomide.com> (raw)
In-Reply-To: <20180314135315.11215-1-peter.ujfalusi@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [180314 06:54]:
> Hi,
> 
> Changes since v1 (sent by Tero):
> - Rebased on linux-next
> - Split the dts and binding document patch
> - Tested it on omap5-uevm that the HPPLL of twl6040 is working (xtal clock is
>   suplied)
> 
> The v1 of this series was sent about two years ago:
> http://linux-arm-kernel.infradead.narkive.com/hBBbM4D7/patch-0-5-arm-omap5-add-support-for-fref-xtal-clk
> 
> but for some reason it was not applied back then, but I have been rolling it on
> top of linux-next ever since.

OK applying into omap-for-v4.17/soc and omap-for-v4.17/dt thanks.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] ARM: OMAP5: add support for fref-xtal-clk
Date: Tue, 20 Mar 2018 08:09:11 -0700	[thread overview]
Message-ID: <20180320150911.GA5799@atomide.com> (raw)
In-Reply-To: <20180314135315.11215-1-peter.ujfalusi@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [180314 06:54]:
> Hi,
> 
> Changes since v1 (sent by Tero):
> - Rebased on linux-next
> - Split the dts and binding document patch
> - Tested it on omap5-uevm that the HPPLL of twl6040 is working (xtal clock is
>   suplied)
> 
> The v1 of this series was sent about two years ago:
> http://linux-arm-kernel.infradead.narkive.com/hBBbM4D7/patch-0-5-arm-omap5-add-support-for-fref-xtal-clk
> 
> but for some reason it was not applied back then, but I have been rolling it on
> top of linux-next ever since.

OK applying into omap-for-v4.17/soc and omap-for-v4.17/dt thanks.

Regards,

Tony

  parent reply	other threads:[~2018-03-20 15:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 13:53 [PATCH v2 0/6] ARM: OMAP5: add support for fref-xtal-clk Peter Ujfalusi
2018-03-14 13:53 ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 1/6] ARM: omap2+: control: add support for auxiliary control module instances Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 2/6] dt-bindings: omap5: ctrl: Support for control module wkup pad config Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 3/6] ARM: dts: omap5: add support " Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 4/6] ARM: OMAP5: control: " Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 5/6] ARM: dts: omap5: add fref_xtal_ck support Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-14 13:53 ` [PATCH v2 6/6] ARM: dts: omap5-board-common: Add phandle for mclk clock for twl6040 Peter Ujfalusi
2018-03-14 13:53   ` Peter Ujfalusi
2018-03-20 15:09 ` Tony Lindgren [this message]
2018-03-20 15:09   ` [PATCH v2 0/6] ARM: OMAP5: add support for fref-xtal-clk Tony Lindgren

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=20180320150911.GA5799@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=t-kristo@ti.com \
    /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.