From: Andrew Morton <akpm@linux-foundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shuah Khan <shuah@kernel.org>, "Hu.Yadi" <hu.yadi@h3c.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: linux-next: manual merge of the kselftest-fixes tree with the mm-hotfixes tree
Date: Mon, 29 Jan 2024 14:28:43 -0800 [thread overview]
Message-ID: <20240129142843.982dd12d63dc2d86a1e415ec@linux-foundation.org> (raw)
In-Reply-To: <c29848d6-29ca-4338-bbdc-abdc71cdd5f4@linuxfoundation.org>
On Mon, 29 Jan 2024 12:01:53 -0700 Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 1/28/24 14:53, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the kselftest-fixes tree got a conflict in:
> >
> > tools/testing/selftests/core/close_range_test.c
> >
> > between commit:
> >
> > 27a593e3f13a ("selftests: core: include linux/close_range.h for CLOSE_RANGE_* macros")
> >
> > from the mm-hotfixes-unstable branch of the mm-hotfixes tree and commit:
> >
> > b5a8a6de69bc ("selftests/core: Fix build issue with CLOSE_RANGE_UNSHARE")
> >
> > from the kselftest-fixes tree.
> >
> > I fixed it up (basically the same patch, I used the former which kept
> > the blank line) 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.
> >
>
> Thank you Stephen.
>
> Andrew, would you like me to drop this commit? I was planning to send
> pull request with this in later on today, but if you prefer, I can
> drop this commit and the send the PR.
It was in the batch of hotfixes I sent to Linus yesterday.
next prev parent reply other threads:[~2024-01-29 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 21:53 linux-next: manual merge of the kselftest-fixes tree with the mm-hotfixes tree Stephen Rothwell
2024-01-29 19:01 ` Shuah Khan
2024-01-29 22:28 ` Andrew Morton [this message]
2024-01-29 22:31 ` Shuah Khan
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=20240129142843.982dd12d63dc2d86a1e415ec@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hu.yadi@h3c.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=usama.anjum@collabora.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