All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Cc: Duanqiang Wen <duanqiangwen@net-swift.com>,
	mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clkdev: report over-sized strings when creating clkdev entries
Date: Wed, 01 May 2024 17:59:16 -0700	[thread overview]
Message-ID: <e15b8a1165a5437ab1fa868ccd0b629c.sboyd@kernel.org> (raw)
In-Reply-To: <E1rl62V-004UFh-Te@rmk-PC.armlinux.org.uk>

Quoting Russell King (Oracle) (2024-03-15 04:47:55)
> Report an error when an attempt to register a clkdev entry results in a
> truncated string so the problem can be easily spotted.
> 
> Reported by: Duanqiang Wen <duanqiangwen@net-swift.com>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> ---

Applied to clk-next

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Cc: Duanqiang Wen <duanqiangwen@net-swift.com>,
	mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clkdev: report over-sized strings when creating clkdev entries
Date: Wed, 01 May 2024 17:59:16 -0700	[thread overview]
Message-ID: <e15b8a1165a5437ab1fa868ccd0b629c.sboyd@kernel.org> (raw)
In-Reply-To: <E1rl62V-004UFh-Te@rmk-PC.armlinux.org.uk>

Quoting Russell King (Oracle) (2024-03-15 04:47:55)
> Report an error when an attempt to register a clkdev entry results in a
> truncated string so the problem can be easily spotted.
> 
> Reported by: Duanqiang Wen <duanqiangwen@net-swift.com>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> ---

Applied to clk-next

_______________________________________________
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-02  0:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 11:47 [PATCH] clkdev: report over-sized strings when creating clkdev entries Russell King (Oracle)
2024-03-15 11:47 ` Russell King (Oracle)
2024-04-08  3:48 ` Stephen Boyd
2024-04-08  3:48   ` Stephen Boyd
2024-05-02  0:59 ` Stephen Boyd [this message]
2024-05-02  0:59   ` Stephen Boyd
2024-05-02  1:02   ` Stephen Boyd
2024-05-02  1:02     ` Stephen Boyd
2024-05-02  8:02     ` Russell King (Oracle)
2024-05-02  8:02       ` Russell King (Oracle)
2024-05-02  8:22       ` Russell King (Oracle)
2024-05-02  8:22         ` Russell King (Oracle)
2024-05-02 11:08         ` Russell King (Oracle)
2024-05-02 11:08           ` Russell King (Oracle)
2024-05-02 22:18           ` Stephen Boyd
2024-05-02 22:18             ` Stephen Boyd
2024-05-17 22:09 ` Guenter Roeck
2024-05-17 22:09   ` Guenter Roeck
2024-05-17 22:22   ` Russell King (Oracle)
2024-05-17 22:22     ` Russell King (Oracle)
2024-05-17 23:34     ` Guenter Roeck
2024-05-17 23:34       ` Guenter Roeck
2024-05-17 23:37       ` Russell King (Oracle)
2024-05-17 23:37         ` Russell King (Oracle)
2024-05-18  3:24         ` Guenter Roeck
2024-05-18  3:24           ` Guenter Roeck
2024-05-18  7:01           ` Russell King (Oracle)
2024-05-18  7:01             ` Russell King (Oracle)
2024-05-22  6:53             ` Linux regression tracking (Thorsten Leemhuis)
2024-05-22  6:53               ` Linux regression tracking (Thorsten Leemhuis)
2024-05-22  9:34               ` Russell King (Oracle)
2024-05-22  9:34                 ` Russell King (Oracle)
2024-05-22  9:37                 ` Russell King (Oracle)
2024-05-22  9:37                   ` Russell King (Oracle)
2024-05-22 21:32                 ` Guenter Roeck
2024-05-22 21:32                   ` Guenter Roeck
2024-05-18 13:44   ` Guenter Roeck
2024-05-18 13:44     ` Guenter Roeck

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=e15b8a1165a5437ab1fa868ccd0b629c.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=duanqiangwen@net-swift.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rmk+kernel@armlinux.org.uk \
    /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.