From: Paulo Alcantara <pc@manguebit.org>
To: Mark Brown <broonie@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
linux-next@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: -next for CIFS
Date: Mon, 24 Aug 2026 10:26:28 -0300 [thread overview]
Message-ID: <250be9700243abbc7e08406856b93357@manguebit.org> (raw)
In-Reply-To: <e2f818f5-c2cd-4975-9be8-f73101a36081@sirena.org.uk>
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!
next prev parent reply other threads:[~2026-08-24 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 12:42 -next for CIFS Paulo Alcantara
2026-08-24 13:05 ` Mark Brown
2026-08-24 13:26 ` Paulo Alcantara [this message]
2026-08-29 0:05 ` Paulo Alcantara
2026-08-29 0:42 ` Mark Brown
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=250be9700243abbc7e08406856b93357@manguebit.org \
--to=pc@manguebit.org \
--cc=broonie@kernel.org \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-next@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