From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] efi patch queue 2018-07-25
Date: Mon, 30 Jul 2018 12:16:25 -0400 [thread overview]
Message-ID: <20180730161625.GD32145@bill-the-cat> (raw)
In-Reply-To: <796bd774-06bc-1f06-403d-17b163f7015d@suse.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 <trini@konsulko.com> 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 <xypron.glpk@gmx.de>
> >>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: <http://lists.denx.de/pipermail/u-boot/attachments/20180730/2b961a6c/attachment.sig>
next prev parent reply other threads:[~2018-07-30 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 13:04 [U-Boot] [PULL] efi patch queue 2018-07-25 Alexander Graf
2018-07-28 15:55 ` Tom Rini
2018-07-28 16:07 ` Heinrich Schuchardt
2018-07-28 16:13 ` Tom Rini
2018-07-28 16:21 ` Heinrich Schuchardt
2018-07-28 16:32 ` Tom Rini
2018-07-28 17:10 ` Heinrich Schuchardt
2018-07-28 18:33 ` Tom Rini
2018-07-28 21:32 ` Heinrich Schuchardt
2018-07-29 1:33 ` Tom Rini
2018-07-29 7:42 ` Heinrich Schuchardt
2018-07-30 16:13 ` Tom Rini
2018-07-30 23:56 ` Tom Rini
2018-07-30 16:05 ` Simon Glass
2018-07-30 16:14 ` Alexander Graf
2018-07-30 16:16 ` Tom Rini [this message]
2018-07-31 1:36 ` Tom Rini
2018-07-31 8:19 ` Alexander Graf
2018-08-07 17:12 ` Simon Glass
2018-08-07 17:41 ` Tom Rini
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=20180730161625.GD32145@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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