All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@aol.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/erofs-utils: new package
Date: Thu, 19 Mar 2020 21:25:58 +0800	[thread overview]
Message-ID: <20200319132546.GA5552@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20200318223950.GC10025@scaer>

Hi Yann,

On Wed, Mar 18, 2020 at 11:39:50PM +0100, Yann E. MORIN wrote:
> Gao, All,
> 
> On 2020-03-16 09:58 +0800, Gao Xiang spake thusly:
> > This patch adds EROFS userspace tool erofs-utils to buildroot,
> > which can be used to generate EROFS images.
> > 
> > Signed-off-by: Gao Xiang <hsiangkao@aol.com>
> 
> Applied to master, with the following fixes:
> 
>   - add explicit --enable-lz4
>   - explain why autoreconf
>   - add DEVELOPPER entry
> 
> Thanks!

Thanks for taking time & your help on this patch, it looks good
to me. :)

And if possible, could you also kindly consider [PATCH v2 2/2]?

I have been verified this series by booting up generated rootfs
images with no unexpected behavior, kindly let me know if
something else needed.

Thanks,
Gao Xiang

  reply	other threads:[~2020-03-19 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200316015838.15183-1-hsiangkao.ref@aol.com>
2020-03-16  1:58 ` [Buildroot] [PATCH v2 1/2] package/erofs-utils: new package Gao Xiang
2020-03-16  1:58   ` [Buildroot] [PATCH v2 2/2] fs/erofs: add support for creating EROFS rootfs image Gao Xiang
2020-03-19 17:49     ` Yann E. MORIN
2020-03-20  7:13       ` Gao Xiang
2020-03-20 20:20         ` Yann E. MORIN
2020-03-18 22:39   ` [Buildroot] [PATCH v2 1/2] package/erofs-utils: new package Yann E. MORIN
2020-03-19 13:25     ` Gao Xiang [this message]
2020-03-19 16:44       ` Yann E. MORIN
2020-03-20  7:05         ` 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=20200319132546.GA5552@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=hsiangkao@aol.com \
    --cc=buildroot@busybox.net \
    /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.