mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yury Norov <yury.norov@gmail.com>
Cc: 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 mm tree with the bitmap tree
Date: Sun, 10 Jul 2022 09:07:56 +0200	[thread overview]
Message-ID: <54caa91f8b430e03770854d916f6eae27a7d63f9.camel@svanheule.net> (raw)
In-Reply-To: <20220704172609.27ec5d8c@canb.auug.org.au>

Hi Stephen,

On Mon, 2022-07-04 at 17:26 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 4 Jul 2022 16:58:41 +1000 Stephen Rothwell <sfr@canb.auug.org.au>
> wrote:
> > 
> > Today's linux-next merge of the mm tree got a conflict in:
> > 
> >   include/linux/cpumask.h
> > 
> > between commits:
> > 
> >   50e413c31800 ("lib/cpumask: change return types to unsigned")
> >   e32bd0390739 ("lib/cpumask: move one-line wrappers around find_bit to the
> > header")
> > 
> > from the bitmap tree and commits:
> > 
> >   2b0b9f2665b2 ("cpumask: Fix invalid uniprocessor mask assumption")
> >   284d22458843 ("cpumask: update cpumask_next_wrap() signature")
> > 
> > from the mm tree.
> > 
> > I fixed it up (I hope, 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.
> 

Thanks for solving the conflicts, looks fine to me. I've asked Andrew to reorder
my patches. The end result for the series should be the same though, and I don't
think my patches should require too many changes anymore.

If further merge conflicts arise with Yury's cpumask patches, I'm also fine with
them being run as one series if that would make things easier.

Best,
Sander

  reply	other threads:[~2022-07-10  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  6:58 Stephen Rothwell
2022-07-04  7:26 ` Stephen Rothwell
2022-07-10  7:07   ` Sander Vanheule [this message]
2022-07-04  7:13 Stephen Rothwell
2022-07-15 11:14 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=54caa91f8b430e03770854d916f6eae27a7d63f9.camel@svanheule.net \
    --to=sander@svanheule.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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

all inboxes | Powered by JetHome®