> On Oct 6, 2021, at 2:57 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > Hi Nick, > > On Wed, 6 Oct 2021 12:17:24 -0700 Nick Terrell <nickrterrell@xxxxxxxxx> wrote: >> >> From: Nick Terrell <terrelln@xxxxxx> >> >> The following changes since commit 9e1ff307c779ce1f0f810c7ecce3d95bbae40896: >> >> Linux 5.15-rc4 (2021-10-03 14:08:47 -0700) >> >> are available in the Git repository at: >> >> https://github.com/terrelln/linux.git zstd-1.4.10 >> >> for you to fetch changes up to a0ccd980d5048053578f3b524e3cd3f5d980a9c5: >> >> MAINTAINERS: Add maintainer entry for zstd (2021-10-04 20:04:32 -0700) >> >> I would like to merge this pull request into linux-next to bake, and then submit >> the PR to Linux in the 5.16 merge window. If you have been a part of the >> discussion, are a maintainer of a caller of zstd, tested this code, or otherwise >> been involved, thank you! And could you please respond below with an appropiate >> tag, so I can collect support for the PR > > Added to linux-next 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. Thanks Stephen!
