From: Tom Rini <trini@konsulko.com>
To: Huang Jianan <jnhuang95@gmail.com>
Cc: u-boot@lists.denx.de, linux-erofs@lists.ozlabs.org, xiang@kernel.org
Subject: Re: [PATCH v4 0/5] fs/erofs: new filesystem
Date: Sat, 5 Mar 2022 09:57:02 -0500 [thread overview]
Message-ID: <20220305145702.GA5020@bill-the-cat> (raw)
In-Reply-To: <3d6e3fb8-1b96-6f45-0aa9-9f330ee71432@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Sat, Mar 05, 2022 at 09:06:36PM +0800, Huang Jianan wrote:
>
>
> 在 2022/3/4 3:15, Tom Rini 写道:
> > On Thu, Mar 03, 2022 at 10:51:18PM +0800, Huang Jianan wrote:
> >
> > > Hi Tom,
> > >
> > > Would you mind taking some time to check if this version meets
> > > the requirements ?So we could have a chance to be merged
> > > into the next version ?
> > >
> > > I have triggered a CI via Github PR based on this version :
> > > https://github.com/u-boot/u-boot/pull/133
> > It seems fine, yes. The thing about that PR is that it doesn't use a
> > custom build of the Docker container that also has the tools, so the FS
> > tests aren't actually run. I'll do that when I get to testing and
> > applying this, but if you can do that before hand to ensure the tests
> > really do run and pass, especially on Azure where things can be a tiny
> > bit trickier (since source directory is enforced read-only), that would
> > be great.
> I verified the test on my own machine, but I overlooked that the container
> used in CI is prebuilt ...
> I replaced the container in the .azure-pipelines.yml with my own build and
> re-triggered the CI on this PR. Now I can see from the log that the newly
> added test_erofs is working properly.
Great, thanks for confirming!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-03-05 14:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 7:05 [PATCH v4 0/5] fs/erofs: new filesystem Huang Jianan
2022-02-26 7:05 ` [PATCH v4 1/5] fs/erofs: add erofs filesystem support Huang Jianan
2022-03-16 12:10 ` Tom Rini
2022-02-26 7:05 ` [PATCH v4 2/5] lib/lz4: update LZ4 decompressor module Huang Jianan
2022-03-16 12:10 ` Tom Rini
2024-05-24 14:26 ` Jonathan Liu
2024-05-24 16:52 ` Gao Xiang
2024-05-26 8:06 ` Jonathan Liu
2024-05-26 12:18 ` Jianan Huang
2024-05-28 13:28 ` Jonathan Liu
2024-05-28 14:03 ` Gao Xiang
2022-02-26 7:05 ` [PATCH v4 3/5] fs/erofs: add lz4 decompression support Huang Jianan
2022-03-16 12:10 ` Tom Rini
2022-02-26 7:05 ` [PATCH v4 4/5] fs/erofs: add filesystem commands Huang Jianan
2022-03-16 12:10 ` Tom Rini
2022-02-26 7:05 ` [PATCH v4 5/5] test/py: Add tests for the erofs Huang Jianan
2022-03-16 12:10 ` Tom Rini
2022-03-03 14:51 ` [PATCH v4 0/5] fs/erofs: new filesystem Huang Jianan
2022-03-03 19:15 ` Tom Rini
2022-03-05 13:06 ` Huang Jianan
2022-03-05 14:57 ` Tom Rini [this message]
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=20220305145702.GA5020@bill-the-cat \
--to=trini@konsulko.com \
--cc=jnhuang95@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=u-boot@lists.denx.de \
--cc=xiang@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