From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Meson clock fixes for 4.13-rc4
Date: Mon, 31 Jul 2017 23:43:08 +0200 [thread overview]
Message-ID: <1501537388.2759.7.camel@baylibre.com> (raw)
In-Reply-To: <20170731202031.GK2146@codeaurora.org>
On Mon, 2017-07-31 at 13:20 -0700, Stephen Boyd wrote:
> On 07/31, Neil Armstrong wrote:
> > Hi Mike, Stephen,
> >
> > Here is some fixes for Meson GXBB and Meson8 drivers, that could go for
> > 4.13-rc4.
> >
>
> Are any of these critical fixes for regressions in the v4.13-rc
> series? All the Fixes tags look like they go back to before
> v4.13-rc1, so they don't look critical at first glance. If
> anything, they're mostly nice to have non-critical fixes? If so,
> can we defer these until the next merge window?
I agree that these fixes hardly qualify as critical, except maybe for the mpll
fix. The clock rate actually applied can be really off compared to what CCF will
except to have set.
These fixes are quite simple and safe, it would be nice if we could avoid having
the next version tagged with known issues.
>
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>,
Neil Armstrong <narmstrong@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Meson clock fixes for 4.13-rc4
Date: Mon, 31 Jul 2017 23:43:08 +0200 [thread overview]
Message-ID: <1501537388.2759.7.camel@baylibre.com> (raw)
In-Reply-To: <20170731202031.GK2146@codeaurora.org>
On Mon, 2017-07-31 at 13:20 -0700, Stephen Boyd wrote:
> On 07/31, Neil Armstrong wrote:
> > Hi Mike, Stephen,
> >
> > Here is some fixes for Meson GXBB and Meson8 drivers, that could go for
> > 4.13-rc4.
> >
>
> Are any of these critical fixes for regressions in the v4.13-rc
> series? All the Fixes tags look like they go back to before
> v4.13-rc1, so they don't look critical at first glance. If
> anything, they're mostly nice to have non-critical fixes? If so,
> can we defer these until the next merge window?
I agree that these fixes hardly qualify as critical, except maybe for the mpll
fix. The clock rate actually applied can be really off compared to what CCF will
except to have set.
These fixes are quite simple and safe, it would be nice if we could avoid having
the next version tagged with known issues.
>
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Meson clock fixes for 4.13-rc4
Date: Mon, 31 Jul 2017 23:43:08 +0200 [thread overview]
Message-ID: <1501537388.2759.7.camel@baylibre.com> (raw)
In-Reply-To: <20170731202031.GK2146@codeaurora.org>
On Mon, 2017-07-31 at 13:20 -0700, Stephen Boyd wrote:
> On 07/31, Neil Armstrong wrote:
> > Hi Mike, Stephen,
> >
> > Here is some fixes for Meson GXBB and Meson8 drivers, that could go for
> > 4.13-rc4.
> >
>
> Are any of these critical fixes for regressions in the v4.13-rc
> series? All the Fixes tags look like they go back to before
> v4.13-rc1, so they don't look critical at first glance. If
> anything, they're mostly nice to have non-critical fixes? If so,
> can we defer these until the next merge window?
I agree that these fixes hardly qualify as critical, except maybe for the mpll
fix. The clock rate actually applied can be really off compared to what CCF will
except to have set.
These fixes are quite simple and safe, it would be nice if we could avoid having
the next version tagged with known issues.
>
next prev parent reply other threads:[~2017-07-31 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 9:25 [GIT PULL] Meson clock fixes for 4.13-rc4 Neil Armstrong
2017-07-31 9:25 ` Neil Armstrong
2017-07-31 9:25 ` Neil Armstrong
2017-07-31 20:20 ` Stephen Boyd
2017-07-31 20:20 ` Stephen Boyd
2017-07-31 20:20 ` Stephen Boyd
2017-07-31 21:43 ` Jerome Brunet [this message]
2017-07-31 21:43 ` Jerome Brunet
2017-07-31 21:43 ` Jerome Brunet
2017-08-01 1:38 ` Stephen Boyd
2017-08-01 1:38 ` Stephen Boyd
2017-08-01 1:38 ` Stephen Boyd
2017-08-01 12:11 ` Neil Armstrong
2017-08-01 12:11 ` Neil Armstrong
2017-08-01 12:11 ` Neil Armstrong
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=1501537388.2759.7.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@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 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.