From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Tom Rini <trini@konsulko.com>, Qu Wenruo <wqu@suse.com>
Cc: u-boot@lists.denx.de, marek.behun@nic.cz,
linux-btrfs@vger.kernel.org, jnhuang95@gmail.com,
linux-erofs@lists.ozlabs.org, joaomarcos.costa@bootlin.com,
thomas.petazzoni@bootlin.com, miquel.raynal@bootlin.com
Subject: Re: [PATCH v2 1/8] fs: fat: unexport file_fat_read_at()
Date: Sat, 6 Aug 2022 06:44:38 +0800 [thread overview]
Message-ID: <99d73f60-868c-28e9-e862-04a934e741ef@gmx.com> (raw)
In-Reply-To: <20220805211420.GA3027583@bill-the-cat>
On 2022/8/6 05:14, Tom Rini wrote:
> On Tue, Jul 26, 2022 at 01:22:09PM +0800, Qu Wenruo wrote:
>
>> That function is only utilized inside fat driver, unexport it.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> Unfortunately, the series fails CI:
> https://source.denx.de/u-boot/u-boot/-/jobs/478838
>
OK, it's a bug in the unsupported fses (which squashfs doesn't support)
The actual read bytes is not updated.
Sorry for the inconvenience.
Any idea that how to run the full tests locally so I can prevent such
problem?
Thanks,
Qu
WARNING: multiple messages have this Message-ID (diff)
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Tom Rini <trini@konsulko.com>, Qu Wenruo <wqu@suse.com>
Cc: joaomarcos.costa@bootlin.com, marek.behun@nic.cz,
u-boot@lists.denx.de, thomas.petazzoni@bootlin.com,
miquel.raynal@bootlin.com, linux-erofs@lists.ozlabs.org,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/8] fs: fat: unexport file_fat_read_at()
Date: Sat, 6 Aug 2022 06:44:38 +0800 [thread overview]
Message-ID: <99d73f60-868c-28e9-e862-04a934e741ef@gmx.com> (raw)
In-Reply-To: <20220805211420.GA3027583@bill-the-cat>
On 2022/8/6 05:14, Tom Rini wrote:
> On Tue, Jul 26, 2022 at 01:22:09PM +0800, Qu Wenruo wrote:
>
>> That function is only utilized inside fat driver, unexport it.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> Unfortunately, the series fails CI:
> https://source.denx.de/u-boot/u-boot/-/jobs/478838
>
OK, it's a bug in the unsupported fses (which squashfs doesn't support)
The actual read bytes is not updated.
Sorry for the inconvenience.
Any idea that how to run the full tests locally so I can prevent such
problem?
Thanks,
Qu
next prev parent reply other threads:[~2022-08-05 22:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 5:22 [PATCH v2 0/8] U-boot: fs: add generic unaligned read offset handling Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 1/8] fs: fat: unexport file_fat_read_at() Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-08-05 21:14 ` Tom Rini
2022-08-05 21:14 ` Tom Rini
2022-08-05 22:44 ` Qu Wenruo [this message]
2022-08-05 22:44 ` Qu Wenruo
2022-08-06 2:44 ` Tom Rini
2022-08-06 2:44 ` Tom Rini
2022-07-26 5:22 ` [PATCH v2 2/8] fs: btrfs: fix a bug which no data get read if the length is not 0 Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 3/8] fs: btrfs: fix a crash if specified range is beyond file size Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 4/8] fs: btrfs: move the unaligned read code to _fs_read() for btrfs Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 5/8] fs: ext4: rely on _fs_read() to handle leading unaligned block read Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 6/8] fs: fat: rely on higher layer to get block aligned read range Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 7/8] fs: ubifs: rely on higher layer to do unaligned read Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo via Linux-erofs
2022-07-26 5:22 ` [PATCH v2 8/8] fs: erofs: add unaligned read range handling Qu Wenruo
2022-07-26 5:22 ` Qu Wenruo 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=99d73f60-868c-28e9-e862-04a934e741ef@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=jnhuang95@gmail.com \
--cc=joaomarcos.costa@bootlin.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=marek.behun@nic.cz \
--cc=miquel.raynal@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wqu@suse.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 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.