Re: -next for CIFS
Mark Brown <[email protected]>
| Newsgroups | org.kernel.vger.linux-next |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Aug 24, 2026 at 09:42:20AM -0300, Paulo Alcantara wrote:
> The new -next for CIFS patches are in
> https://git.manguebit.org/linux.git cifs-next
Thanks, I've updated and will use this tree from tomorrow.
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.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmqMQZYACgkQJNaLcl1U h9Cmiwf+J56XHxJnvyw+5flhXiTFDkVFGtTZrtdXDy1CijU2CChEmg6Pydiqe8z2 60jQ1BmLsMBJ30IEM/uHnnVStyYoUOoEtfbK94e8nyOmt2RT3IP8i1F4UWZ0VZwF PRFjHDEANxcjcwW65bXOcSGPbOHmDGmu5cpolPjAecTK88lLjdqMKOS2nVletlMx 46XALjZgIRXRzzH8J5Ek4Rbu9uDgIag9My5enBJTVkaEVrj4DJl+X1j35qkHRioE xy3/DIQKE1KzlP2w/yHNHo/7ffpVq/ieHCHkUIHljEOYRuYfES1et733zvhAQocR PCaVSF9R24U4apHujFepnq2bE39TXQ== =H2Yn -----END PGP SIGNATURE-----