From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: buildbot kicked off for current for-next (patches for 5.5)
Date: Sat, 2 Nov 2019 21:36:31 -0500 [thread overview]
Message-ID: <CAH2r5mv8O0R1ath7fe+G0ENcv8fC-MXda4h7GHEun-4TCE7EyA@mail.gmail.com> (raw)
Buildbot regression tests kicked off for 19 cifs/smb3 patches
(including most of Aurelien's multichannel e.g.) - things destined for
5.5
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/277
--
Thanks,
Steve
reply other threads:[~2019-11-03 2:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAH2r5mv8O0R1ath7fe+G0ENcv8fC-MXda4h7GHEun-4TCE7EyA@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs@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;
as well as URLs for NNTP newsgroup(s).