All of lore.kernel.org
 help / color / mirror / Atom feed
From: Etienne Carriere <etienne.carriere@linaro.org>
To: u-boot@lists.denx.de
Subject: STM32MP1: Adding TF-A causes kernel errors
Date: Wed, 30 Sep 2020 17:20:39 +0200	[thread overview]
Message-ID: <CAN5uoS92U99c+UW641CbqGmOo8eTOkSN02kaXzL6FAuoqOzmnw@mail.gmail.com> (raw)
In-Reply-To: <20200930130620.GX14816@bill-the-cat>

Hi Yann, Tom and all,

On Wed, 30 Sep 2020 at 15:06, Tom Rini <trini@konsulko.com> wrote:
>
> On Wed, Sep 30, 2020 at 12:03:06PM +0200, Marek Vasut wrote:
> > On 9/30/20 11:51 AM, Jan Kiszka wrote:
> > > [BCC'ed TF-A only, migrating to u-boot, including folks involved there]
> > >
> > > On 30.09.20 11:20, Yann GAUTIER wrote:
> > >> Hi Jan,
> > >>
> > >> After discussing with my colleagues, it seems there are 2 issues there.
> > >> One patch is missing in U-Boot:
> > >> http://patchwork.ozlabs.org/project/uboot/patch/20200605092244.1.I773bf523d9f4d1a6212483d030e34113b832a779 at changeid/
> > >>
> > >
> > > I can confirm that this resolves the errors I've seen.
> > >
> > > Will that patch still hit 2020.10?
> >
> > Is that patch a bugfix or a feature ? OpTee seems like a feature.
> > Since it has no Fixes: tag, it seems like a feature?
>
> That linked commit could/should be a Fixes tag it looks like at first
> read.
>

Yes, I agree with you. This is definitely a fixup.

Regards,
Etienne

> --
> Tom

  reply	other threads:[~2020-09-30 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d643d22d-58c5-1e02-d5be-cb26d3902c37@web.de>
     [not found] ` <fcf2dbe2-c5d8-7042-5c59-ab9bcb1e612d@web.de>
     [not found]   ` <e5533f9b-bf88-526d-5594-a719d928f01c@st.com>
     [not found]     ` <746e3c3b-7b2a-f815-a000-bcb2c31317cb@web.de>
     [not found]       ` <6a493688-6c0f-6e8b-d072-88855236e677@st.com>
2020-09-30  9:51         ` STM32MP1: Adding TF-A causes kernel errors Jan Kiszka
2020-09-30 10:03           ` Marek Vasut
2020-09-30 10:05             ` Jan Kiszka
2020-09-30 13:06             ` Tom Rini
2020-09-30 15:20               ` Etienne Carriere [this message]
2020-10-01  9:52           ` Jan Kiszka
2020-10-05  6:07             ` Jan Kiszka
2020-10-12 22:02               ` Jan Kiszka
2020-10-12 22:02                 ` Jan Kiszka
2020-10-13 11:06                 ` Patrick DELAUNAY
2020-10-13 11:06                   ` Patrick DELAUNAY
2020-10-13 14:26                   ` Jan Kiszka
2020-10-13 14:26                     ` Jan Kiszka
2020-10-15  9:45                     ` Jan Kiszka
2020-10-15  9:45                       ` Jan Kiszka

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=CAN5uoS92U99c+UW641CbqGmOo8eTOkSN02kaXzL6FAuoqOzmnw@mail.gmail.com \
    --to=etienne.carriere@linaro.org \
    --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 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.