mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Chao Yu <yuchao0@huawei.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<devel@driverdev.osuosl.org>, <linux-erofs@lists.ozlabs.org>,
	Chao Yu <chao@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	<weidu.du@huawei.com>, Fang Wei <fangwei1@huawei.com>,
	Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH 2/2] staging: erofs: complete POSIX ACL support
Date: Fri, 25 Jan 2019 21:54:42 +0800	[thread overview]
Message-ID: <c3007962-c73f-ddfc-eb39-d8d8b5fef832@huawei.com> (raw)
In-Reply-To: <20190125133044.GC1795@kadam>

Hi Dan,

On 2019/1/25 21:30, Dan Carpenter wrote:
> On Fri, Jan 25, 2019 at 08:01:04PM +0800, Gao Xiang wrote:
>> Let's add .get_acl() to read the file's acl
>> from its xattrs to make POSIX ACL usable.
>>
>> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
>> ---
>>  This [PATCH 2/2] currently hasn't tested, please ignore temporarily...
>>  I will test it asap...
> 
> This is an awkward thing.
> 
> Just don't send it until after you test it.  We also ignore RFC patches
> so if you mark it as RFC that will be ignored if you want.

Yes, you are right.

Actually I just want to send the only [PATCH 1/2], but I missed to
change the subject of [PATCH 1/2] -> [PATCH]...Therefore I have to
send this incomplete one to complete this "patchset" by mistake...

Thanks,
Gao Xiang

> 
> regards,
> dan carpenter
> 

  reply	other threads:[~2019-01-25 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 11:51 [PATCH 1/2] staging: erofs: use xattr_prefix to wrap up Gao Xiang
2019-01-25 12:01 ` [PATCH 2/2] staging: erofs: complete POSIX ACL support Gao Xiang
2019-01-25 13:30   ` Dan Carpenter
2019-01-25 13:54     ` Gao Xiang [this message]
2019-01-25 13:26 ` [PATCH 1/2] staging: erofs: use xattr_prefix to wrap up Dan Carpenter
2019-01-25 13:58   ` Gao Xiang

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=c3007962-c73f-ddfc-eb39-d8d8b5fef832@huawei.com \
    --to=gaoxiang25@huawei.com \
    --cc=chao@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fangwei1@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=weidu.du@huawei.com \
    --cc=yuchao0@huawei.com \
    /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
all inboxes | Powered by JetHome®