mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] staging: erofs: add requirements field in superblock
Date: Sun, 16 Jun 2019 14:47:56 +0800	[thread overview]
Message-ID: <8ba384bd-44ea-2261-4f49-da354298edf6@huawei.com> (raw)
In-Reply-To: <20190615221606.1C12F2183F@mail.kernel.org>

Hi Sasha,

On 2019/6/16 6:16, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: ba2b77a82022 staging: erofs: add super block operations.
> 
> The bot has tested the following trees: v5.1.9, v4.19.50.
> 
> v5.1.9: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.19.50: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> 
> How should we proceed with this patch?

I will manually make patches for v5.1.9 and v4.19.50
after it gets merged.

Thanks,
Gao Xiang

> 
> --
> Thanks,
> Sasha
> 

  parent reply	other threads:[~2019-06-16  6:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  2:42 [PATCH v2 " Gao Xiang
2019-06-11  2:42 ` [PATCH v2 2/2] staging: erofs: rename data_mapping_mode to datamode Gao Xiang
2019-06-11  3:01 ` [PATCH v2 1/2] staging: erofs: add requirements field in superblock Chao Yu
2019-06-13  8:35 ` [PATCH v3 " Gao Xiang
     [not found]   ` <20190615221606.1C12F2183F@mail.kernel.org>
2019-06-16  6:47     ` Gao Xiang [this message]
2019-06-16  7:00   ` Gao Xiang
2019-06-16  7:14     ` Greg Kroah-Hartman
2019-06-16  7:21       ` 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=8ba384bd-44ea-2261-4f49-da354298edf6@huawei.com \
    --to=gaoxiang25@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®