public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	Yury Norov <yury.norov@gmail.com>
Subject: Re: linux-next: manual merge of the tip tree with the mm tree
Date: Wed, 17 Jul 2024 09:27:08 +1000	[thread overview]
Message-ID: <20240717092708.0a40aca4@canb.auug.org.au> (raw)
In-Reply-To: <20240612112746.3130d68b@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

Hi all,

On Wed, 12 Jun 2024 11:27:46 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the tip tree got a conflict in:
> 
>   include/linux/cacheinfo.h
> 
> between commit:
> 
>   f6a9651bfd74 ("cpumask: make core headers including cpumask_types.h where possible")
> 
> from the mm-nonmm-unstable branch of the mm tree and commit:
> 
>   685cb1674060 ("cacheinfo: Add function to get cacheinfo for a given CPU and cache level")
> 
> from the tip 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.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc include/linux/cacheinfo.h
> index 286db104e054,3dde175f4108..000000000000
> --- a/include/linux/cacheinfo.h
> +++ b/include/linux/cacheinfo.h
> @@@ -3,7 -3,8 +3,8 @@@
>   #define _LINUX_CACHEINFO_H
>   
>   #include <linux/bitops.h>
> + #include <linux/cpuhplock.h>
>  -#include <linux/cpumask.h>
>  +#include <linux/cpumask_types.h>
>   #include <linux/smp.h>
>   
>   struct device_node;

This is now a conflict between the mm-nonmm-stable tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-07-16 23:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  1:27 linux-next: manual merge of the tip tree with the mm tree Stephen Rothwell
2024-07-16 23:27 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-07  4:14 Stephen Rothwell
2025-03-07  7:20 ` Thomas Weißschuh
2025-03-07  7:58 ` Andrew Morton
2025-03-07 21:54   ` Jeff Xu
2025-02-24  3:42 Stephen Rothwell
2025-02-24  5:50 ` Anshuman Khandual
2025-03-26  1:05 ` Stephen Rothwell
2025-01-10  2:47 Stephen Rothwell
2024-12-09  2:24 Stephen Rothwell
2025-01-06  3:09 ` Stephen Rothwell
2025-01-06 20:21   ` Suren Baghdasaryan
2025-01-06 21:14     ` Stephen Rothwell
2025-01-06 21:15       ` Suren Baghdasaryan
2024-09-11  5:16 Stephen Rothwell
2024-09-05  5:35 Stephen Rothwell
2024-09-10 23:23 ` Stephen Rothwell
2024-04-05  0:51 Stephen Rothwell
2024-04-07 23:50 ` Stephen Rothwell
2023-03-21 23:33 Stephen Rothwell

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=20240717092708.0a40aca4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=yury.norov@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