From: Mark Brown <broonie@kernel.org>
To: Paulo Alcantara <pc@manguebit.org>
Cc: David Howells <dhowells@redhat.com>,
linux-next@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: -next for CIFS
Date: Sat, 29 Aug 2026 01:42:12 +0100 [thread overview]
Message-ID: <apIq5P0XbbRHDf37@sirena.co.uk> (raw)
In-Reply-To: <752329b497166aed63d62ceb9c663012@manguebit.org>
[-- 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 --]
prev parent reply other threads:[~2026-08-29 0:42 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
2026-08-29 0:05 ` Paulo Alcantara
2026-08-29 0:42 ` Mark Brown [this message]
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=apIq5P0XbbRHDf37@sirena.co.uk \
--to=broonie@kernel.org \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pc@manguebit.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