From: Greg KH <gregkh@linuxfoundation.org>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Sasha Levin <Alexander.Levin@microsoft.com>
Subject: Re: [GIT PULL] commits for Linux 4.16
Date: Thu, 10 May 2018 12:47:07 +0200 [thread overview]
Message-ID: <20180510104707.GA7059@kroah.com> (raw)
In-Reply-To: <CAKaJLVsimnZ-HnUgN-CXzyhtGRQkSTqwuMzf=AED-Y2Vd_M-tg@mail.gmail.com>
On Thu, May 10, 2018 at 01:36:14PM +0300, Sam Protsenko wrote:
> On 10 May 2018 at 08:47, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Hi,
> >
> > First off, properly trim your quoting, I had to dig for your response...
> >
>
> Got it, sorry.
>
> > On Thu, May 10, 2018 at 12:44:21AM +0300, Sam Protsenko wrote:
> >> > Tero Kristo (1):
> >> > clk: ti: fix flag space conflict with clkctrl clocks
> >> >
> >>
> >> Hi Greg,
> >>
> >> Can we please pull this one to 4.16-stable? It fixes boot on
> >> BeagleBone Black. This bug was mentioned here: [1].
> >>
> >> Thanks!
> >>
> >> [1] https://www.spinics.net/lists/arm-kernel/msg643873.html
> >
> > What is the git commit id of the patch? I need that to get this merged
> > properly.
> >
>
> 1. Patch that fixes BBB (in mainline, between 4.16 and 4.17) -- it's
> the one that should be merged:
>
> 269bd202bc0fd04e841cb123867fd3f49e04ace9
> clk: ti: fix flag space conflict with clkctrl clocks
>
> 2. Patch that breaks BBB (in mainline, between 4.15 and 4.16) -- just
> for information:
>
> c083dc5f3738d394223baa0f90705397b0844acd
> clk: ti: am33xx: add set-rate-parent support for display clkctrl clock
Why does the patch say:
Fixes: 49159a9dc3da ("clk: ti: add support for CLK_SET_RATE_PARENT flag")
instead of c083dc5f3738 ("clk: ti: am33xx: add set-rate-parent support for display clkctrl clock")
?
Anyway, I'll go queue up 269bd202bc0fd04e841cb123867fd3f49e04ace9,
thanks.
greg k-h
next prev parent reply other threads:[~2018-05-10 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 2:00 [GIT PULL] commits for Linux 4.16 Sasha Levin
2018-05-01 22:09 ` Greg KH
2018-05-02 0:00 ` Sasha Levin
2018-05-02 15:55 ` Greg KH
2018-05-09 21:44 ` Sam Protsenko
2018-05-10 5:47 ` Greg KH
2018-05-10 10:36 ` Sam Protsenko
2018-05-10 10:47 ` Greg KH [this message]
2018-05-10 11:50 ` Sam Protsenko
2018-05-11 6:13 ` Tero Kristo
-- strict thread matches above, loose matches on Subject: below --
2018-05-19 16:58 Sasha Levin
2018-05-27 15:36 ` Greg KH
2018-06-05 4:00 Sasha Levin
2018-06-07 1:07 Sasha Levin
2018-06-17 11:24 ` Greg KH
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=20180510104707.GA7059@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=semen.protsenko@linaro.org \
--cc=stable@vger.kernel.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).