linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ben Schneider <ben@bens.haus>
To: Andrew Lunn <andrew@lunn.ch>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: "Pali Rohár" <pali@kernel.org>,
	"Linux Arm Kernel" <linux-arm-kernel@lists.infradead.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: enable 1200Mhz clock speed for armada-37xx
Date: Thu, 11 Jul 2024 18:59:59 +0200 (GMT+02:00)	[thread overview]
Message-ID: <O1XjBTq--3-9@bens.haus> (raw)
In-Reply-To: <dce98e50-6b50-4d4e-abe2-8419a675d25e@lunn.ch>

Jun 5, 2024, 16:44 by andrew@lunn.ch:

> On Wed, Jun 05, 2024 at 09:44:22PM +0200, Pali Rohár wrote:
>
>> So, go ahead with this change with my
>>
>> Reviewed-by: Pali Rohár <pali@kernel.org>
>>
>
> I defer to your knowledge in this matter.
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
>  Andrew
>

Hi all, just checking in to see if there are any outstanding concerns/issues outstanding with this patch? I am happy to report several more weeks of stability on two A3720 devices. Thanks!

Ben


  reply	other threads:[~2024-07-11 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  1:26 [PATCH] cpufreq: enable 1200Mhz clock speed for armada-37xx Benjamin Schneider
2024-06-03  1:26 ` Benjamin Schneider
2024-06-03 12:46   ` Andrew Lunn
2024-06-03 19:33     ` Ben Schneider
2024-06-05 19:44   ` Pali Rohár
2024-06-05 23:44     ` Andrew Lunn
2024-07-11 16:59       ` Ben Schneider [this message]
2024-07-16  8:51         ` Gregory CLEMENT
2024-09-09 13:00           ` Ben Schneider
2024-10-13  3:01           ` Ben Schneider
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25 21:14 bschnei
2024-12-12  7:07 ` Viresh Kumar
2024-12-15 21:23   ` Marek Behún
2025-01-12 22:49     ` Ben Schneider
2025-02-03 10:57     ` Viresh Kumar
2025-02-19  5:52 ` Viresh Kumar

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=O1XjBTq--3-9@bens.haus \
    --to=ben@bens.haus \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    /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).