linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] pwm: Fixes for v5.4-rc6
Date: Tue, 5 Nov 2019 22:31:27 +0100	[thread overview]
Message-ID: <20191105213127.gyxc2shjz2nq7ul5@pengutronix.de> (raw)
In-Reply-To: <20191102134800.3847540-1-thierry.reding@gmail.com>

Hello Thierry,

On Sat, Nov 02, 2019 at 02:48:00PM +0100, Thierry Reding wrote:
> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
> 
>   Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git tags/pwm/for-5.4-rc6
> 
> for you to fetch changes up to 40a6b9a00930fd6b59aa2eb6135abc2efe5440c3:
> 
>   Revert "pwm: Let pwm_get_state() return the last implemented state" (2019-10-21 16:48:52 +0200)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> pwm: Fixes for v5.4-rc6
> 
> It turned out that relying solely on drivers storing all the PWM state
> in hardware was a little premature and causes a number of subtle (and
> some not so subtle) regressions. Revert the offending patch for now.
> 
> ----------------------------------------------------------------
> Thierry Reding (1):
>       Revert "pwm: Let pwm_get_state() return the last implemented state"

In a different thread on the pwm mailing list I suggested to add

	pwm: bcm-iproc: prevent unloading the driver module while in use

to this pull request. You didn't comment and didn't add it. :-|
(https://patchwork.ozlabs.org/patch/1178972/)

While this is not a recent regression (it was introduced in 4.8-rc1) I
think it's still worth to be fixed, don't you agree?
 
Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      parent reply	other threads:[~2019-11-05 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 13:48 [GIT PULL] pwm: Fixes for v5.4-rc6 Thierry Reding
2019-11-02 18:35 ` pr-tracker-bot
2019-11-05 21:31 ` Uwe Kleine-König [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=20191105213127.gyxc2shjz2nq7ul5@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=torvalds@linux-foundation.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).