From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: stable@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: request for 4.14-stable: 00c5a926af12 ("clk: mvebu: use correct bit for 98DX3236 NAND")
Date: Mon, 19 Nov 2018 11:43:48 +0100 [thread overview]
Message-ID: <20181119104348.GA26120@kroah.com> (raw)
In-Reply-To: <20181111193645.ae72nh3sxisdg2io@debian>
On Sun, Nov 11, 2018 at 07:36:45PM +0000, Sudip Mukherjee wrote:
> Hi Greg,
>
> This was not marked for stable but seems it should be in stable.
> Please apply to your queue of 4.14-stable.
>
> --
> Regards
> Sudip
> >From 0b08b65ad657c08a9b8468d64624f6df52a2f863 Mon Sep 17 00:00:00 2001
> From: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Date: Thu, 24 May 2018 17:23:41 +1200
> Subject: [PATCH] clk: mvebu: use correct bit for 98DX3236 NAND
>
> commit 00c5a926af12a9f0236928dab3dc9faf621406a1 upstream
>
> The correct fieldbit value for the NAND PLL reload trigger is 27.
>
> Fixes: commit e120c17a70e5 ("clk: mvebu: support for 98DX3236 SoC")
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> ---
> drivers/clk/mvebu/clk-corediv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2018-11-19 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 19:36 request for 4.14-stable: 00c5a926af12 ("clk: mvebu: use correct bit for 98DX3236 NAND") Sudip Mukherjee
2018-11-19 10:43 ` Greg Kroah-Hartman [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=20181119104348.GA26120@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox