From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-clk <linux-clk@vger.kernel.org>,
lkft-triage@lists.linaro.org,
open list <linux-kernel@vger.kernel.org>,
Anders Roxell <anders.roxell@linaro.org>,
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: Thu, 16 May 2024 12:32:45 +0100 [thread overview]
Message-ID: <ZkXu3XNVLhTuRRNt@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYurPNaW=u2E+h+segnXhY3cfWo3BJpfYDJxKRFPY4epsQ@mail.gmail.com>
On Thu, May 16, 2024 at 12:27:20PM +0200, Naresh Kamboju wrote:
> On Wed, 15 May 2024 at 22:53, Russell King (Oracle)
> <linux@armlinux.org.uk> wrote:
> >
> > On Tue, May 07, 2024 at 01:26:17PM -0700, Stephen Boyd 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?
> > >
> > > [1] https://lore.kernel.org/r/20240507065317.3214186-1-m.szyprowski@samsung.com
> >
> > This one has (I think) ended up in the patch system last week, but it's
> > not clkdev, it's only related. I'm also not Cc'd on its posting, and
> > it's not posted to any mailing list that I'm a part of. So I've not
> > been following any discussion on it.
> >
> > Digging in to the discussion, I see various attributations, and a final
> > message reporting an unused variable, and a promise to send v2. So,
> > I'm guessing that
> > http://www.home.armlinux.org.uk/developer/patches/viewpatch.php?id=9397/1
>
> I do not have access to this link ^.
Sorry, that's my internal link, the external one is:
http://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9397/1
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-16 11:33 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
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) [this message]
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=ZkXu3XNVLhTuRRNt@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=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=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 NNTP newsgroup(s).