From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 30 Jul 2018 12:16:25 -0400 Subject: [U-Boot] [PULL] efi patch queue 2018-07-25 In-Reply-To: <796bd774-06bc-1f06-403d-17b163f7015d@suse.de> References: <20180725130427.60884-1-agraf@suse.de> <20180728155508.GL7590@bill-the-cat> <796bd774-06bc-1f06-403d-17b163f7015d@suse.de> Message-ID: <20180730161625.GD32145@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Jul 30, 2018 at 06:14:16PM +0200, Alexander Graf wrote: > On 07/30/2018 06:05 PM, Simon Glass wrote: > >Hi, > > > >On 28 July 2018 at 09:55, Tom Rini wrote: > >>On Wed, Jul 25, 2018 at 03:04:27PM +0200, Alexander Graf wrote: > >> > >>>Hi Tom, > >>> > >>>This is my current patch queue for efi. Please pull. > >>> > >>>Alex > >>> > >>> > >>>The following changes since commit 323a73adc9a1bf2de43fe03bdd9c3038ce7c2784: > >>> > >>> mtd: nand: add new enum for storing ECC algorithm (2018-07-23 14:33:21 -0400) > >>> > >>>are available in the git repository at: > >>> > >>> git://github.com/agraf/u-boot.git tags/signed-efi-next > >>> > >>>for you to fetch changes up to 0b8a88ab6aa24de0ef2bf1e8109409f71e770a8e: > >>> > >>> MAINTAINERS: assign lib/charset.c (2018-07-25 15:00:24 +0200) > >>> > >>NAK, this breaks one of the filesystem tests. Specifically: > >>commit 0dc1bfb7302d220a48364263d5632d6d572b069b > >>Author: Heinrich Schuchardt > >>Date: Mon Jul 2 02:41:23 2018 +0200 > >> > >> fs: fat: cannot write to subdirectories > >> > >>Breaks TC13: 1MB write to ./1MB.file.w2 > >This is getting a little painful for me :-) > > > >The EFI tree contains a few of the patches needed to make sandbox > >support EFI, but not all. A rebase on this tree provides me with a > >segfault, so it needs more work. But we are right at RC1. > > > >Looking at the state of things it is clear that I cannot just pull in > >my previously applied patches since there are various changes. I'm > >going to have to send a new set of patches. > > > >Perhaps as a way forward we could drop this one patch and apply to > >master? Then I can do my side of things while the patch is worked on? > > What is really missing to just make the test pass? All we need to do is > adapt the fail/success rate of the fat test, right? > > How do I quickly run the test to cook up a patch? Run ./test/fs/fs-test.sh and see what you get for totals, as the starting point. And then you can also join in on cringing at how bad our current filesystem related tests are :) -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: