From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] turbostat 2024.04.27 for linux-next
Date: Mon, 29 Apr 2024 07:52:08 +1000 [thread overview]
Message-ID: <20240429075208.79fc86de@canb.auug.org.au> (raw)
In-Reply-To: <CAJvTdKmqJx5nnwfxehRRHrYi7mR=6Y8bbrwL083Ain=MhBQq6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Hi Len,
On Sat, 27 Apr 2024 23:02:12 -0400 Len Brown <lenb@kernel.org> wrote:
>
> Please add this branch to linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git next
>
> Currently, and in the foreseeable future, I will stage some upstream-bound
> user-space power management utility work on this branch.
>
> I do not expect any other trees to touch these files,
> including Rafael's pm/linux-next branch,
> and so it should merge without conflicts.
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb.auug.org.au
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-04-28 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 3:02 [GIT PULL] turbostat 2024.04.27 for linux-next Len Brown
2024-04-28 21:52 ` Stephen Rothwell [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=20240429075208.79fc86de@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).