mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	"Russell King (Oracle)" <linux@armlinux.org.uk>
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>
Subject: Re: clkdev: report over-sized strings when creating clkdev entries
Date: Thu, 16 May 2024 12:57:53 +0200	[thread overview]
Message-ID: <29f30eda-deba-4092-9b4c-8cb101b8691d@samsung.com> (raw)
In-Reply-To: <CA+G9fYurPNaW=u2E+h+segnXhY3cfWo3BJpfYDJxKRFPY4epsQ@mail.gmail.com>

On 16.05.2024 12:27, 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
>> https://protect2.fireeye.com/v1/url?k=946226d9-f5e933ef-9463ad96-74fe485fffe0-28286a0026513387&q=1&e=a16c1c53-9c99-475a-b144-8adf7852ebc0&u=http%3A%2F%2Fwww.home.armlinux.org.uk%2Fdeveloper%2Fpatches%2Fviewpatch.php%3Fid%3D9397%2F1
> I do not have access to this link ^.
>
>> is now superseded in some way... I wouldn't have known without locating
>> this email and checking the links.


The fix for drivers/clk/samsung/clk.c driver has been merged to clk-next:

https://lore.kernel.org/all/f7a877622829db499bf2bc65fe9ffbff.sboyd@kernel.org/

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


  reply	other threads:[~2024-05-16 10:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  7:20 Naresh Kamboju
2024-05-07  7:44 ` 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 [this message]
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=29f30eda-deba-4092-9b4c-8cb101b8691d@samsung.com \
    --to=m.szyprowski@samsung.com \
    --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=linux@armlinux.org.uk \
    --cc=lkft-triage@lists.linaro.org \
    --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

all inboxes | Powered by JetHome®