Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nikita Shubin" <nikita.shubin@maquefel.me>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Alexander Sverdlin" <alexander.sverdlin@gmail.com>
Cc: "Hartley Sweeten" <hsweeten@visionengravers.com>,
	"Russell King" <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate()
Date: Wed, 11 Sep 2024 14:54:28 +0000	[thread overview]
Message-ID: <a1ceab99-f26c-4edb-8f72-12abf20eec9f@app.fastmail.com> (raw)
In-Reply-To: <246de2986dce9d867894bb006a1b2b3601e94a4e.camel@maquefel.me>

On Wed, Sep 11, 2024, at 08:14, Nikita Shubin wrote:
> Hi Dan!
>
> Reviewed-by: Nikita Shubin <nikita.shubin@maquefel.me>
>
> Alexander, Arnd
>
> unfortunately, the ep93xx DT conversion series is also affected by this
> bug.

Here is what I did now:

1. applied Dan's patch on a new branch
2. applied the DT conversion series on top of that,
   removing that file.
3. applied the first patch (with minor context changes)
   in drivers/clk/clk-ep93xx.c again, along with
   the MODULE_LICENSE fix I did.
4. finally, merged the entire branch into my for-next
   branch so it actually makes it into linux-next

My plan now is to keep the branch in linux-next for at
least a week and send all the other pull requests for
the merge window first. If no other problems show up
(either with this branch or my other 6.12 contents),
I hope to send it all later in the merge window. If
something goes wrong, I'll send only the bugfix as part
of my first fixes branch for 6.12 and we'll defer the
DT conversion once more.

I should have merged it earlier, but wasn't sure about
interdependencies with the parts that already got merged
elsewhere and with the comments about DTC warnings.

From what I can tell, the current state is as good as
it gets, as we'll always get more comments or conflicts
with new reversions of the series. Let's hope we can
address any other issues on top of what I've merged
now and stop rebasing.

    Arnd


  reply	other threads:[~2024-09-11 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  7:39 [PATCH] ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate() Dan Carpenter
2024-09-11  7:52 ` Alexander Sverdlin
2024-09-11  8:14 ` Nikita Shubin
2024-09-11 14:54   ` Arnd Bergmann [this message]
2024-09-11 14:59     ` Alexander Sverdlin
2024-09-11 16:28       ` Nikita Shubin

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=a1ceab99-f26c-4edb-8f72-12abf20eec9f@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=alexander.sverdlin@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=hsweeten@visionengravers.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=nikita.shubin@maquefel.me \
    /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