Message ID | CAJvTdKmqJx5nnwfxehRRHrYi7mR=6Y8bbrwL083Ain=MhBQq6g@mail.gmail.com (mailing list archive) |
---|---|
State | Accepted, archived |
Headers | show |
Series | [GIT,PULL] turbostat 2024.04.27 for linux-next | expand |
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.