From: Tony Lindgren <tony@atomide.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] clk: ti: clkctrl driver updates for 4.16 merge window
Date: Mon, 11 Dec 2017 10:29:08 -0800 [thread overview]
Message-ID: <20171211182908.GA14441@atomide.com> (raw)
In-Reply-To: <CAEG3pNDDOcdFCqsH3849NeWucoAvKJ0iVQjxf3-E+=Wsb-j1Gg@mail.gmail.com>
* Michael Turquette <mturquette@baylibre.com> [171211 17:21]:
> On Mon, Dec 11, 2017 at 8:40 AM, Tero Kristo <t-kristo@ti.com> wrote:
> > On 11/12/17 17:29, Tony Lindgren wrote:
> >>
> >> * Michael Turquette <mturquette@baylibre.com> [171207 18:41]:
> >>>
> >>> Hi Tero,
> >>>
> >>> On Thu, Dec 7, 2017 at 12:09 AM, Tero Kristo <t-kristo@ti.com> wrote:
> >>>>
> >>>> On 07/12/17 09:29, Stephen Boyd wrote:
> >>>>>
> >>>>>
> >>>>> On 12/05, Tero Kristo wrote:
> >>>>>>
> >>>>>>
> >>>>>> Hi Stephen, Mike,
> >>>>>>
> >>>>>> This pull request contains the v2 of the series posted
> >>>>>> (https://www.spinics.net/lists/linux-omap/msg140042.html), with
> >>>>>> Stephen's acks added to the mentioned patches, and just applied on
> >>>>>> top of 4.15-rc1. I actually wonder if you wanted to add your acks to
> >>>>>> the rest of the patches also, but couldn't find any comment about
> >>>>>> this anywhere.
> >>>>>>
> >>>>>> -Tero
> >>>>>>
> >>>>>> ====
> >>>>>>
> >>>>>> The following changes since commit
> >>>>>> 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
> >>>>>>
> >>>>>> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
> >>>>>>
> >>>>>> are available in the git repository at:
> >>>>>>
> >>>>>> https://github.com/t-kristo/linux-pm.git 4.15-rc1-clkctrl-driver
> >>>>>>
> >>>>>> for you to fetch changes up to
> >>>>>> fe7020e64f042db4b5ca50c358b232e866523447:
> >>>>>>
> >>>>>> clk: ti: omap4: clkctrl data fixes for opt-clocks (2017-12-01
> >>>>>> 15:18:08 +0200)
> >>>>>
> >>>>>
> >>>>>
> >>>>> Pulled into clk-next.
> >>>>
> >>>>
> >>>>
> >>>> Thanks.
> >>>>
> >>>>> Did you want to sign a tag instead of
> >>>>> sending a plain branch? My ack isn't necessary on anything.
> >>>>>
> >>>>
> >>>> Just a plain branch. Never signed a tag so far, do you have guidelines
> >>>> someplace if you prefer this in future?
> >>>
> >>>
> >>> "git tag -s" is all you need to know. It's nice to keep that tag on
> >>> your public tree until the next -rc1, but not strictly necessary.
> >>>
> >>> Ideally PRs should used signed tags, as it lets us verify a trusted tree.
> >>
> >>
> >> Looks like I need to merge in Tero's commit fe7020e64f04 above for the
> >> related the dts changes. Can we all consider commit fe7020e64f04
> >> immutable?
> >
> >
> > From my point of view at least, its frozen.
>
> +1
>
> Mike
OK thanks will merge commit fe7020e64f04 into my omap-for-v4.16/dt-clk
branch too.
Regards,
Tony
prev parent reply other threads:[~2017-12-11 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 12:41 [GIT PULL] clk: ti: clkctrl driver updates for 4.16 merge window Tero Kristo
2017-12-07 7:29 ` Stephen Boyd
2017-12-07 8:09 ` Tero Kristo
2017-12-07 18:38 ` Michael Turquette
2017-12-11 15:29 ` Tony Lindgren
2017-12-11 16:40 ` Tero Kristo
2017-12-11 17:19 ` Michael Turquette
2017-12-11 18:29 ` Tony Lindgren [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=20171211182908.GA14441@atomide.com \
--to=tony@atomide.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--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.