From: Shuah Khan <skhan@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Shuah Khan <shuah@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: John Stultz <jstultz@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: manual merge of the kselftest tree with the tip tree
Date: Tue, 16 Apr 2024 17:54:05 -0600 [thread overview]
Message-ID: <69d0c6c6-ed82-410c-9102-09ed3b95ae05@linuxfoundation.org> (raw)
In-Reply-To: <20240412155545.7b8ad20b@canb.auug.org.au>
On 4/11/24 23:55, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kselftest tree got a conflict in:
>
> tools/testing/selftests/timers/valid-adjtimex.c
>
> between commit:
>
> 076361362122 ("selftests: timers: Fix valid-adjtimex signed left-shift undefined behavior")
>
> from the tip tree and commit:
>
> 8e222dcf92a8 ("selftests: timers: Fix valid-adjtimex signed left-shift undefined behavior")
>
> from the kselftest tree.
>
Thank you. I dropped 8e222dcf92a8 from linux-kselftest next
> Slightly different versions of the same patch (whitespace differences).
>
> I fixed it up (I (arbitrarily) used the former version) 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,
-- Shuah
prev parent reply other threads:[~2024-04-16 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 5:55 Stephen Rothwell
2024-04-16 23:54 ` Shuah Khan [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=69d0c6c6-ed82-410c-9102-09ed3b95ae05@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=shuah@kernel.org \
--cc=tglx@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®