From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] part_efi: fix protective_mbr struct allocation
Date: Wed, 19 Feb 2014 11:08:03 +0100 [thread overview]
Message-ID: <20140219110803.5b558b91@lilith> (raw)
In-Reply-To: <20140219091904.055671f0@amdc2363>
Hi Lukasz,
On Wed, 19 Feb 2014 09:19:04 +0100, Lukasz Majewski
<l.majewski@samsung.com> wrote:
> Hi Albert, Tom
>
> > Hi Lukasz,
> >
> > On Wed, 12 Feb 2014 21:45:41 +0100, Lukasz Majewski
> > <l.majewski@majess.pl> wrote:
> >
> > > I think, that the patch for fixing the unaligned access in this
> > > function has already been posted by Piotr Wilczek. We have
> > > experienced similar issues with Samsung's Exynos4 based targets.
> > >
> > > [PATCH V2] disk:efi: avoid unaligned access on efi partition
> > >
> > > Despite its disappearance from patchwork it shall be available at
> > > mailing list archive.
> > >
> > > The v1 can be found at the following link:
> > > http://patchwork.ozlabs.org/patch/282753/
> >
> > Neither V1 nor V2 have disappeared from patchwork. A "filter" on the
> > subject, selecting "any" state and "both" archived and non-archived
> > patches will return both:
> >
> > V1: http://patchwork.ozlabs.org/patch/282753/ (New)
> > V2: http://patchwork.ozlabs.org/patch/314717/ (Deferred)
> >
> > (I think that the patchwork web interface does not make it possible at
> > all to remove a patch anyway)
>
> Thanks for pointing out. Now it is perfectly visible :-)
>
> >
> > > Inclusion of v2 has been postponed since there was a discussion if
> > > we shall allow unaligned access (-mno-unaligned-access flag) at
> > > armv7 (after patches posted by Tom).
> > >
> > > As fair as I can tell, we will keep the current approach so, I think
> > > that Tom will be willing to pull this patch (v2) now.
> >
> > Agreed, but then we should make sure no one has comments on V2 that
> > they might have withheld due to the initial rejection of V2.
>
> Any comments?
>
> This patch do fix unaligned access problem on Trats2 (Exynos4412), when
> we restore/create GPT, so I would like to know if there are any new
> inquires regarding this patch.
Does not seem to be, so I will apply V2.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-02-19 10:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:40 [U-Boot] [PATCH] part_efi: fix protective_mbr struct allocation Hector Palacios
2014-02-12 14:43 ` Fabio Estevam
2014-02-12 16:33 ` Albert ARIBAUD
2014-02-12 17:33 ` Fabio Estevam
2014-02-12 17:58 ` Albert ARIBAUD
2014-02-12 15:55 ` Lukasz Majewski
2014-02-12 16:24 ` Palacios, Hector
2014-02-12 16:30 ` Albert ARIBAUD
2014-02-12 16:48 ` Palacios, Hector
2014-02-12 20:45 ` Lukasz Majewski
2014-02-13 2:23 ` Albert ARIBAUD
2014-02-19 8:19 ` Lukasz Majewski
2014-02-19 10:08 ` Albert ARIBAUD [this message]
2014-02-19 10:15 ` Albert ARIBAUD
2014-02-19 12:52 ` Palacios, Hector
2014-02-19 14:14 ` Albert ARIBAUD
2014-02-19 14:25 ` Lukasz Majewski
2014-02-19 14:38 ` Albert ARIBAUD
2014-02-19 15:11 ` Lukasz Majewski
2014-02-19 14:22 ` Tom Rini
2014-02-19 15:10 ` Lukasz Majewski
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=20140219110803.5b558b91@lilith \
--to=albert.u.boot@aribaud.net \
--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