From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Li Guifu <blucerlee@gmail.com>
Cc: linux-erofs@lists.ozlabs.org, Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH 2/2] erofs-utils: set up all compiler/linker variables independently
Date: Thu, 14 Nov 2019 08:26:54 +0800 [thread overview]
Message-ID: <20191114002651.GB2809@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <f38afa9b-7a81-d952-bc44-7c6c89aa477a@gmail.com>
Hi Guifu,
On Thu, Nov 14, 2019 at 01:12:26AM +0800, Li Guifu wrote:
> Gao Xiang
> Can you resend this patch ? It is conflict with uuid.
> uuid patch :
> https://lore.kernel.org/linux-erofs/d4d8127a-c452-f7d4-b3b1-50098cf07e12@gmail.com/T/#u
You're right. I'll sort out all erofs-utils pending patches,
rebase this patch and resend soon.
Thanks,
Gao Xiang
>
> On 2019/11/12 19:26, Gao Xiang wrote:
> > Otherwise, the following checking will be effected
> > and it can cause unexpected behavior on configuring.
> >
> > Founded by the upcoming XZ algorithm patches.
> >
> > Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
> > ---
next prev parent reply other threads:[~2019-11-14 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 11:26 [PATCH 1/2] erofs-utils: complete missing memory handling Gao Xiang
2019-11-12 11:26 ` [PATCH 2/2] erofs-utils: set up all compiler/linker variables independently Gao Xiang
2019-11-13 17:12 ` Li Guifu
2019-11-14 0:26 ` Gao Xiang via Linux-erofs [this message]
2019-11-14 13:45 ` [PATCH v2] " Gao Xiang via Linux-erofs
2019-11-14 15:27 ` Li Guifu
2019-11-13 17:03 ` [PATCH v2] erofs-utils: complete missing memory handling Li Guifu
2019-11-14 0:24 ` Gao Xiang via Linux-erofs
2019-11-14 1:51 ` Gao Xiang
2019-11-14 9:19 ` [PATCH v3] " Gao Xiang via Linux-erofs
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=20191114002651.GB2809@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=linux-erofs@lists.ozlabs.org \
--cc=blucerlee@gmail.com \
--cc=hsiangkao@aol.com \
--cc=miaoxie@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;
as well as URLs for NNTP newsgroup(s).