* -next for CIFS
@ 2026-08-24 12:42 Paulo Alcantara
2026-08-24 13:05 ` Mark Brown
0 siblings, 1 reply; 5+ messages in thread
From: Paulo Alcantara @ 2026-08-24 12:42 UTC (permalink / raw)
To: Mark Brown; +Cc: David Howells, linux-next, Namjae Jeon
Hi Mark,
The new -next for CIFS patches are in
https://git.manguebit.org/linux.git cifs-next
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: -next for CIFS
2026-08-24 12:42 -next for CIFS Paulo Alcantara
@ 2026-08-24 13:05 ` Mark Brown
2026-08-24 13:26 ` Paulo Alcantara
2026-08-29 0:05 ` Paulo Alcantara
0 siblings, 2 replies; 5+ messages in thread
From: Mark Brown @ 2026-08-24 13:05 UTC (permalink / raw)
To: Paulo Alcantara; +Cc: David Howells, linux-next, Namjae Jeon
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: -next for CIFS
2026-08-24 13:05 ` Mark Brown
@ 2026-08-24 13:26 ` Paulo Alcantara
2026-08-29 0:05 ` Paulo Alcantara
1 sibling, 0 replies; 5+ messages in thread
From: Paulo Alcantara @ 2026-08-24 13:26 UTC (permalink / raw)
To: Mark Brown; +Cc: David Howells, linux-next, Namjae Jeon
Mark Brown <broonie@kernel.org> writes:
> 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 Mark!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: -next for CIFS
2026-08-24 13:05 ` Mark Brown
2026-08-24 13:26 ` Paulo Alcantara
@ 2026-08-29 0:05 ` Paulo Alcantara
2026-08-29 0:42 ` Mark Brown
1 sibling, 1 reply; 5+ messages in thread
From: Paulo Alcantara @ 2026-08-29 0:05 UTC (permalink / raw)
To: Mark Brown; +Cc: David Howells, linux-next, Namjae Jeon
Hi Mark,
Mark Brown <broonie@kernel.org> writes:
> 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.
I've noticed that CIFS patches from
https://git.manguebit.org/linux.git cifs-next
aren't still appearing in linux-next.
Are you having any issues with it? Please let me know.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: -next for CIFS
2026-08-29 0:05 ` Paulo Alcantara
@ 2026-08-29 0:42 ` Mark Brown
0 siblings, 0 replies; 5+ messages in thread
From: Mark Brown @ 2026-08-29 0:42 UTC (permalink / raw)
To: Paulo Alcantara; +Cc: David Howells, linux-next, Namjae Jeon
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Fri, Aug 28, 2026 at 09:05:57PM -0300, Paulo Alcantara wrote:
> Mark Brown <broonie@kernel.org> writes:
> >> 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.
> I've noticed that CIFS patches from
> https://git.manguebit.org/linux.git cifs-next
> aren't still appearing in linux-next.
> Are you having any issues with it? Please let me know.
Not that I noticed, though it's possible there was some network issue
fetching and got 67176fe3cb4d5cf6fbb821777877bba83efc048f. I have seen
some systems having issues serving stuff with scrapers? I'll check
again on Monday but if nothing else that commit will be there.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-08-29 0:42 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-24 12:42 -next for CIFS Paulo Alcantara
2026-08-24 13:05 ` Mark Brown
2026-08-24 13:26 ` Paulo Alcantara
2026-08-29 0:05 ` Paulo Alcantara
2026-08-29 0:42 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox