From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shuah Khan <shuah@kernel.org>, Andrew Morton <akpm@linux-foundation.org>
Cc: "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>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: linux-next: manual merge of the kselftest-fixes tree with the mm-hotfixes tree
Date: Mon, 29 Jan 2024 08:53:01 +1100 [thread overview]
Message-ID: <20240129085301.5458880a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-01-28 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 21:53 Stephen Rothwell [this message]
2024-01-29 19:01 ` linux-next: manual merge of the kselftest-fixes tree with the mm-hotfixes tree Shuah Khan
2024-01-29 22:28 ` Andrew Morton
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=20240129085301.5458880a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hu.yadi@h3c.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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