public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: linux-next: duplicate patch in the pm tree
Date: Tue, 23 Apr 2024 20:30:42 +0200	[thread overview]
Message-ID: <12425337.O9o76ZdvQC@kreacher> (raw)
In-Reply-To: <20240422081547.7d75d471@canb.auug.org.au>

Hi Stephen,

On Monday, April 22, 2024 12:15:47 AM CEST Stephen Rothwell wrote:
> 
> --Sig_/2mWov6L/1T3YTV5TB80hoeT
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> 
> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different
> commit (but the same patch):
> 
>   6711564863de ("thermal/debugfs: Add missing count increment to thermal_de=
> bug_tz_trip_up()")
> 
> This is commit
> 
>   b552f63cd437 ("thermal/debugfs: Add missing count increment to thermal_de=
> bug_tz_trip_up()")
> 
> in Linus' tree.

Thanks for the report, this should be fixed now in the PM tree.

Cheers,
Rafael




  reply	other threads:[~2024-04-23 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 22:15 linux-next: duplicate patch in the pm tree Stephen Rothwell
2024-04-23 18:30 ` Rafael J. Wysocki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-18  3:27 Stephen Rothwell
2025-07-18 13:33 ` Jonathan Corbet
2024-08-05  1:58 Stephen Rothwell
2024-08-05  3:13 ` Andrew Morton
2023-06-07  4:41 Stephen Rothwell
2023-06-07 21:02 ` Dan Williams
2023-03-26 20:45 Stephen Rothwell
2023-03-27 18:11 ` Wysocki, Rafael J

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=12425337.O9o76ZdvQC@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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