Linux-ARM-Kernel Archive mirror
 help / color / mirror / Atom feed
From: Anders Roxell <anders.roxell@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	 lkft-triage@lists.linaro.org,
	open list <linux-kernel@vger.kernel.org>,
	 Russell King <linux@armlinux.org.uk>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	 Michael Turquette <mturquette@baylibre.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: clkdev: report over-sized strings when creating clkdev entries
Date: Wed, 8 May 2024 06:06:35 +0200	[thread overview]
Message-ID: <CADYN=9LJCHK=TkU8y6jNFVFGNg4v4GtPEUUvvsvJ4it6X00D7A@mail.gmail.com> (raw)
In-Reply-To: <820ddc2ec70780ae1ecd3af864dc8bd6.sboyd@kernel.org>

On Tue, 7 May 2024 at 22:26, Stephen Boyd <sboyd@kernel.org> wrote:
>
> Quoting Arnd Bergmann (2024-05-07 00:44:15)
> > On Tue, May 7, 2024, at 09:20, Naresh Kamboju wrote:
> > > The WinLink E850-96 board boot failed with Linux next-20240506 but there
> > > is no kernel crash log on the serial [1].
> > >
> > > Anders bisection results pointing to this commit,
> > > # first bad commit:
> > >   [4d11c62ca8d77cb1f79054844b598e0f4e92dabe]
> > >   clkdev: report over-sized strings when creating clkdev entrie
> > >
> > > After reverting the above patch the boot test passed [2].
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
>
> There are two fixes on the list: [1] and [2]. Perhaps one of those
> resolves this?

I applied patch [2] ontop of next-20240506 was helpful and the e850-96
board booted.

Cheers,
Anders

>
> [1] https://lore.kernel.org/r/20240507065317.3214186-1-m.szyprowski@samsung.com
> [2] https://lore.kernel.org/r/20240507064434.3213933-1-m.szyprowski@samsung.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-05-08  4:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+G9fYuZd_ur56H8fwDSvUywopvn_b7ogprGkjEatQ7EPTLwYQ@mail.gmail.com>
2024-05-07  7:44 ` clkdev: report over-sized strings when creating clkdev entries Arnd Bergmann
2024-05-07 20:26   ` Stephen Boyd
2024-05-07 20:52     ` Arnd Bergmann
2024-05-07 21:55       ` Stephen Boyd
2024-05-08  4:06     ` Anders Roxell [this message]
2024-05-08 21:07     ` Sam Protsenko
2024-05-08 22:29       ` Russell King (Oracle)
2024-05-15 20:52     ` Russell King (Oracle)
2024-05-16 10:27       ` Naresh Kamboju
2024-05-16 10:57         ` Marek Szyprowski
2024-05-16 11:33           ` Russell King (Oracle)
2024-05-16 11:32         ` Russell King (Oracle)

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='CADYN=9LJCHK=TkU8y6jNFVFGNg4v4GtPEUUvvsvJ4it6X00D7A@mail.gmail.com' \
    --to=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkft-triage@lists.linaro.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mturquette@baylibre.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=sboyd@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).