mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Masney <masneyb@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Brian Masney <bmasney@redhat.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>,
	Kees Cook <kees@kernel.org>, Kees Cook <kees+treewide@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the clk tree with the origin tree
Date: Fri, 13 Nov 2026 15:40:24 -0500	[thread overview]
Message-ID: <avd1uEWBWWFZsKT6@x1g10> (raw)
In-Reply-To: <avch0WAFqmKQHd_1@sirena.org.uk>

Hi Mark,

On Fri, Nov 13, 2026 at 02:42:25PM +0000, Mark Brown wrote:
> Today's linux-next merge of the clk tree got a conflict in:
> 
>   drivers/clk/socfpga/clk-s10.c
> 
> between commit:
> 
>   4dd10fbbeb9c3 ("treewide: Convert devm_kmalloc() family to the devm_kmalloc_obj() family")
> 
> from the origin tree and commit:
> 
>   51805c5218c7e ("clk: socfpga: stratix10: register the SP timer clocks early")

We've had 4 different conflicts in the clk tree this so far this
development cycle with that treewide commit that was introduced in
rc2. The clk-next branch is based off of various topic branches that
are merged into clk-next, so we can easily rebase clk-next. I rebased
clk-next against 7.4-rc2, and kept all of the topic branches at
7.4-rc1 because I don't want to rewrite any history there.

If there's any other merge conflicts within the clk tree this
development cycle with that treewide commit, then Jerome or I can take
care of it on our end.

Brian

  reply	other threads:[~2026-11-13 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 14:42 Mark Brown
2026-11-13 20:40 ` Brian Masney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-13 14:38 Mark Brown
2026-11-13 14:38 Mark Brown
2026-11-10 17:02 Mark Brown

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=avd1uEWBWWFZsKT6@x1g10 \
    --to=masneyb@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=bmasney@redhat.com \
    --cc=broonie@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kees+treewide@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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®