From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: stable@vger.kernel.org, Paul Cercueil <paul@crapouillou.net>,
Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
letux-kernel@openphoenux.org, linux-mips@vger.kernel.org,
tsbogend@alpha.franken.de
Subject: Re: [PATCH] [stable v5.4.x] pwm: jz4740: Fix build failure
Date: Fri, 10 Jul 2020 21:47:02 +0200 [thread overview]
Message-ID: <20200710194702.ire4deel2zn7mnxk@pengutronix.de> (raw)
In-Reply-To: <DB8C7C01-0FBB-4A9F-B068-15C06BBC0873@goldelico.com>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Fri, Jul 10, 2020 at 12:48:36PM +0200, H. Nikolaus Schaller wrote:
>
> > Am 10.07.2020 um 12:27 schrieb Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> >
> > When commit 9017dc4fbd59 ("pwm: jz4740: Enhance precision in calculation
> > of duty cycle") from v5.8-rc1 was backported to v5.4.x its dependency on
> > commit ce1f9cece057 ("pwm: jz4740: Use clocks from TCU driver") was not
> > noticed which made the pwm-jz4740 driver fail to build.
>
> Please can you add my "reported by?"
Greg, can you please add this while applying? (Assuming you're ok with
this change and ideally Paul can confirm the change is fine.)
Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-10 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:27 [PATCH] [stable v5.4.x] pwm: jz4740: Fix build failure Uwe Kleine-König
2020-07-10 10:48 ` H. Nikolaus Schaller
2020-07-10 19:47 ` Uwe Kleine-König [this message]
2020-07-14 16:58 ` 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=20200710194702.ire4deel2zn7mnxk@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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).