linux-kernel - Re: [GIT PULL] thermal material for v6.3, take 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 16 Feb 2023 14:36:42 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Balsam CHIHI <bchihi@...libre.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Niklas Söderlund 
        <niklas.soderlund+renesas@...natech.se>,
        yong qin <yongqin.liu@...aro.org>,
        Vibhav Pant <vibhavp@...il.com>, Alain Volmat <avolmat@...com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM mailing list <linux-pm@...r.kernel.org>
Subject: Re: [GIT PULL] thermal material for v6.3, take 2

Hi Daniel,

On Mon, Feb 13, 2023 at 12:10 PM Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
>
> Hi Rafael,
>
> The following changes since commit 61b7614c114c817f9f326282c2f7a728bf0051a8:
>
>    Merge branch 'thermal-intel' into linux-next (2023-02-09 19:57:59 +0100)

When I was preparing my thermal pull request for 6.3-rc1 which I'm
going to submit shortly, I noticed that this pull request was based on
my linux-next branch which wasn't suitable for this purpose at all (it
contained temporary merges and material that is not sent in thermal
pull requests, like ACPI and power management commits).

In the future, if I receive a pull request based on my linux-next
branch, I won't pull.

Please base your pull requests sent to me on mainline commits
(ideally, on a recent -rc) or, if there are commits that your new
material depends on in my thermal branch, you can base your pull
request on it (it is a forward-only branch as a rule, but please see
below).  If none of the above is applicable, please let me know ahead
of time, so I can set up a separate forward-only branch as a base for
your pull request.

This time I had to reset my thermal branch back to commit
f364beb5b673, merge my thermal-core and thermal-intel branches and
cherry-pick the new thermal changes from the $subject pull request on
top of that to remedy the situation (I have verified that this has not
introduced any code differences).

Thanks,
Rafael