public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	linux-pwm@vger.kernel.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] pwm: Changes for v5.11-rc1
Date: Sat, 19 Dec 2020 01:57:39 +0100	[thread overview]
Message-ID: <X91QA5bXgPXCiS8U@ulmo> (raw)
In-Reply-To: <CAHk-=wgfVj3n5qftaLwk3ZiMiKooO-vzk_XHbcRKPCpBWbtq7w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]

On Fri, Dec 18, 2020 at 12:35:09PM -0800, Linus Torvalds wrote:
> On Fri, Dec 18, 2020 at 8:04 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > This is a fairly big release cycle from the PWM framework's point of
> > view.
> 
> Why does all of this have commit dates from the last day?
> 
> It clearly cannot have been in linux-next in this form, at least.
> 
> I pulled and then unpulled. Don't send me stuff that hasn't been in
> next without a _lot_ of explanations for why, most certainly not the
> week before Christmas.

I didn't realize that this would show up as all new commits. The reason
why this happens is because the first commit in the tree is a fix for an
issue for which Uwe had sent an alternative patch to you directly for
inclusion in v5.10.

After going over the patches again as I was preparing the pull request,
I realized that the commit message was no longer accurate, so I changed
the commit message of the first commit, which then caused all of the
subsequent patches (i.e. all of them) to be rewritten.

The only change that hasn't been in linux-next for at least a week is a
bugfix I merged two days ago. The rest should be identical except for
the commit message on that first commit.

For reference, here's a diff on my for-next branch that the pull request
is based on, compared to what it was like a week ago:

	$ git diff for-next@{8days}..pwm/for-5.11-rc1
	diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
	index cc1eb0818648..ce5c4fc8da6f 100644
	--- a/drivers/pwm/pwm-sun4i.c
	+++ b/drivers/pwm/pwm-sun4i.c
	@@ -294,12 +294,8 @@ static int sun4i_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
	 
		ctrl |= BIT_CH(PWM_CLK_GATING, pwm->hwpwm);
	 
	-       if (state->enabled) {
	+       if (state->enabled)
			ctrl |= BIT_CH(PWM_EN, pwm->hwpwm);
	-       } else {
	-               ctrl &= ~BIT_CH(PWM_EN, pwm->hwpwm);
	-               ctrl &= ~BIT_CH(PWM_CLK_GATING, pwm->hwpwm);
	-       }
	 
		sun4i_pwm_writel(sun4i_pwm, ctrl, PWM_CTRL_REG);
	 

And that corresponds to the topmost patch.

I hope this clarifies things, and sorry for not mentioning this in the
pull request.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-19  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 16:04 [GIT PULL] pwm: Changes for v5.11-rc1 Thierry Reding
2020-12-18 20:35 ` Linus Torvalds
2020-12-19  0:57   ` Thierry Reding [this message]
2020-12-19 19:51     ` Linus Torvalds
2020-12-19 21:06 ` pr-tracker-bot

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=X91QA5bXgPXCiS8U@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.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