mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic SoC updates for v4.15
Date: Mon, 30 Oct 2017 22:52:42 +0100	[thread overview]
Message-ID: <CAFBinCBpDsn1rrUUy74dpkCsHj_wca3ojmCaUUEiVB41cfvTMQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1fLbzp4xzFyTEO1w4vu=X=wwSV74_WBXiuYqTeF1P5ng@mail.gmail.com>

Hi Arnd,

On Mon, Oct 30, 2017 at 11:26 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Sun, Oct 29, 2017 at 5:43 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>
>> ----------------------------------------------------------------
>> Amlogic SoC updates for v4.15
>> - add SMP support to Meson8/8b
>
> Pulled into next/soc. For my understanding, could you clarify what
> this line is needed for on meson?
>
> +textofs-$(CONFIG_ARCH_MESON) := 0x00208000
this was already part of Carlo's version of the SMP patches. I didn't
question this change (I simply assumed that it's relevant - I never
questioned "why" it was relevant) so far
however, that was until Linus L?ssing (CC'ed) investigated a
bug-report from Emiliano Ingrassia (also CC'ed). you can find his
results here: [0]
(tl;dr: kernel refuses to boot without this change when using a
slightly modified multi_v7_defconfig)

Linus even asked me to split this change out into a separate patch [1]
however, by the time I came back home Kevin already sent out the pull request

please let me know if
- we can keep the patches the way they are right now
- or if you want to separate this change into a separate patch


Regards
Martin


[0] https://lkml.org/lkml/2017/10/28/148
[1] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/005155.html

  parent reply	other threads:[~2017-10-30 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 16:43 Kevin Hilman
2017-10-30 10:26 ` Arnd Bergmann
2017-10-30 11:12   ` Kevin Hilman
2017-10-30 21:52   ` Martin Blumenstingl [this message]
2017-11-02 15:49     ` Arnd Bergmann

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=CAFBinCBpDsn1rrUUy74dpkCsHj_wca3ojmCaUUEiVB41cfvTMQ@mail.gmail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=linus-amlogic@lists.infradead.org \
    /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

all inboxes | Powered by JetHome®