All of lore.kernel.org
 help / color / mirror / Atom feed
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
Date: Wed, 15 Jun 2016 21:12:54 +0200	[thread overview]
Message-ID: <20160615191254.GA19579@kozik-lap> (raw)
In-Reply-To: <m2twgupbpl.fsf@baylibre.com>

On Wed, Jun 15, 2016 at 11:07:50AM -0700, Kevin Hilman wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
> 
> > On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> >> arm:
> >> 
> >>     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v7_defconfig+CONFIG_LKDTM=y:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v7_defconfig+CONFIG_EFI=y:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     exynos_defconfig:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v7_defconfig:
> >>         exynos5410-odroidxu: 1 failed lab
> >> 
> >>     multi_v5_defconfig:
> >>         at91sam9261ek: 1 failed lab
> >>         at91sam9m10g45ek: 1 failed lab
> >>         at91sam9x25ek: 1 failed lab
> >>         at91sam9x35ek: 1 failed lab
> >
> > These all seem to have broken after yesterday's merges, adding
> > Alexandre and Krzysztof to Cc here so they can have a look.
> 
> The exynos5410 fails look like the UART3 issue reported earlier and
> which is also happening in linux-next.
> 
> Krzysztof posted a fix[1] that was tested by Javier and myself that
> fixed the problem, but I don't see that upstream yet.
> 
> Krzysztof: did you get that fix submitted yet?
> 
> Kevin
> 
> [1] http://marc.info/?l=linux-kernel&m=146469459503940&w=2

The v2 of it is here:
https://patchwork.kernel.org/patch/9144897/

I do not recall receiving any feedback nor confirmation of applying the patch.
I guess it is time to resend. I'll do it on Thursday.

Best regards,
Krzysztof

  reply	other threads:[~2016-06-15 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5760acd0.571a1c0a.34a58.7333@mx.google.com>
2016-06-15  9:10 ` arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1) Arnd Bergmann
2016-06-15  9:18   ` Alexandre Belloni
2016-06-15 10:50     ` Arnd Bergmann
2016-06-15 18:07   ` Kevin Hilman
2016-06-15 19:12     ` Krzysztof Kozlowski [this message]
2016-06-15 20:08       ` Kevin Hilman

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=20160615191254.GA19579@kozik-lap \
    --to=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@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 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.