mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: linux-next: manual merge of the paulmck tree with the tip tree
Date: Fri, 31 Jul 2026 12:03:18 -0700	[thread overview]
Message-ID: <bc3c02ea-c5bd-4474-9f79-d6079110a7d8@paulmck-laptop> (raw)
In-Reply-To: <amyyLKFqzpkn4BQT@sirena.org.uk>

On Fri, Jul 31, 2026 at 03:33:16PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the paulmck tree got a conflict in:
> 
>   include/linux/hrtimer.h
> 
> between commits:
> 
>   d3dc7fabd4c4a ("hrtimer: Move hrtimer_callback_running() to hrtimer_bases.h")
>   a116c7582d7f7 ("hrtimer: Move hrtimer_update_function() to hrtimer.c")
> 
> from the tip tree and commit:
> 
>   07abbb755f8e3 ("hrtimer: Apply READ_ONCE() to lockless base->running loads")
> 
> from the paulmck tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> This only resolves the conflict, the READ_ONCE() got dropped.
> 
> diff --cc include/linux/hrtimer.h
> index 29072d89e5cb3,b8636e81ca005..0000000000000
> --- a/include/linux/hrtimer.h
> +++ b/include/linux/hrtimer.h

Ouch!  I am pulling this from the pile for the upcoming merge, for the
moment, anyway.

							Thanx, Paul

      reply	other threads:[~2026-07-31 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 14:33 Mark Brown
2026-07-31 19:03 ` Paul E. McKenney [this message]

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=bc3c02ea-c5bd-4474-9f79-d6079110a7d8@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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®