From: "Aurélien Aptel" <aaptel@suse.com>
To: Jonas Witschel <diabonas@archlinux.org>
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH 0/2] cifs-utils: update the cap bounding set only when CAP_SETPCAP is given
Date: Fri, 27 Nov 2020 11:01:37 +0100 [thread overview]
Message-ID: <87zh33dsou.fsf@suse.com> (raw)
In-Reply-To: <20201124133740.cixyh57b3rlto54n@archlinux.org>
Thanks Jonas this is very helpful.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2020-11-27 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 11:11 [PATCH 0/2] cifs-utils: update the cap bounding set only when CAP_SETPCAP is given Jonas Witschel
2020-11-21 11:11 ` [PATCH 1/2] mount.cifs: " Jonas Witschel
2020-11-21 11:11 ` [PATCH 2/2] cifs.upall: " Jonas Witschel
2020-11-24 12:11 ` [PATCH 0/2] cifs-utils: " Aurélien Aptel
2020-11-24 13:37 ` Jonas Witschel
2020-11-27 10:01 ` Aurélien Aptel [this message]
2020-12-09 19:15 ` Pavel Shilovsky
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=87zh33dsou.fsf@suse.com \
--to=aaptel@suse.com \
--cc=diabonas@archlinux.org \
--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).