From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dmitry Torokhov <dmitry.torokhov@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the input tree with Linus' tree
Date: Tue, 20 Aug 2024 11:23:58 +1000 [thread overview]
Message-ID: <20240820112358.665c5532@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hi all,
Today's linux-next merge of the input tree got a conflict in:
drivers/input/touchscreen/cyttsp4_core.c
between commit:
cb04e8b1d2f2 ("minmax: don't use max() in situations that want a C constant expression")
from Linus' tree and commit:
25162a4f64f8 ("Input: cyttsp4 - remove driver")
from the input tree.
I fixed it up (the latter removed the file, so I did that) 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-08-20 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 1:23 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-20 1:37 linux-next: manual merge of the input tree with Linus' tree Stephen Rothwell
2025-08-21 14:57 ` Miguel Ojeda
2022-01-09 23:53 Stephen Rothwell
2021-11-03 23:21 Stephen Rothwell
2020-07-22 4:49 Stephen Rothwell
2013-11-12 1:58 Stephen Rothwell
2012-03-27 1:16 Stephen Rothwell
2012-03-27 7:33 ` Dmitry Torokhov
2010-12-14 2:26 Stephen Rothwell
2010-12-14 18:40 ` Dmitry Torokhov
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=20240820112358.665c5532@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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