All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Miao Xie <miaoxie@huawei.com>,
	LKML <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs: zero out when listxattr is called with no xattr
Date: Tue, 3 Dec 2019 09:52:41 +0800	[thread overview]
Message-ID: <20191203015238.GA210859@architecture4> (raw)
In-Reply-To: <20191202221312.8F590206F0@mail.kernel.org>

Hi Sasha,

On Mon, Dec 02, 2019 at 10:13:11PM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: cadf1ccf1b00 ("staging: erofs: add error handling for xattr submodule").
> 
> The bot has tested the following trees: v5.4.1, v5.3.14, v4.19.87.
> 
> v5.4.1: Build OK!
> v5.3.14: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.19.87: Failed to apply! Possible dependencies:
>     Unable to calculate

Because of file movement, I'll backport manually then.

Thanks,
Gao Xiang

> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?
> 
> -- 
> Thanks,
> Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <gaoxiang25@huawei.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Gao Xiang <hsiangkao@aol.com>, Chao Yu <yuchao0@huawei.com>,
	<linux-erofs@lists.ozlabs.org>,
	LKML <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
	Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH] erofs: zero out when listxattr is called with no xattr
Date: Tue, 3 Dec 2019 09:52:41 +0800	[thread overview]
Message-ID: <20191203015238.GA210859@architecture4> (raw)
In-Reply-To: <20191202221312.8F590206F0@mail.kernel.org>

Hi Sasha,

On Mon, Dec 02, 2019 at 10:13:11PM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: cadf1ccf1b00 ("staging: erofs: add error handling for xattr submodule").
> 
> The bot has tested the following trees: v5.4.1, v5.3.14, v4.19.87.
> 
> v5.4.1: Build OK!
> v5.3.14: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.19.87: Failed to apply! Possible dependencies:
>     Unable to calculate

Because of file movement, I'll backport manually then.

Thanks,
Gao Xiang

> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?
> 
> -- 
> Thanks,
> Sasha

  reply	other threads:[~2019-12-03  1:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191201084040.29275-1-hsiangkao.ref@aol.com>
2019-12-01  8:40 ` [PATCH] erofs: zero out when listxattr is called with no xattr Gao Xiang via Linux-erofs
2019-12-01  8:40   ` Gao Xiang
2019-12-02 22:13   ` Sasha Levin
2019-12-03  1:52     ` Gao Xiang [this message]
2019-12-03  1:52       ` Gao Xiang
2019-12-04  3:14   ` Chao Yu
2019-12-04  3:14     ` Chao Yu

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=20191203015238.GA210859@architecture4 \
    --to=gaoxiang25@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=sashal@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.