public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	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 the pci tree
Date: Fri, 10 Apr 2026 12:55:32 +0100	[thread overview]
Message-ID: <adjlNGglOUTLJ8hF@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

Hi all,

Today's linux-next merge of the input tree got a conflict in:

  drivers/input/mouse/Kconfig

between commit:

  6f468ea360f0a6 ("Input: pc110pad - remove driver")

from the pci tree and commits:

  e732b2ac0a18b6 ("Input: hgpk - remove protocol support")
  8291ffa3e51d6a ("Input: inport - remove driver")
  931e3151dba747 ("Input: logibm - remove driver")

from the input tree.

I fixed it up (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.

diff --cc drivers/input/mouse/Kconfig
index c8b87a87744c28,04d56f40ecb631..00000000000000
--- a/drivers/input/mouse/Kconfig
+++ b/drivers/input/mouse/Kconfig
@@@ -300,32 -290,16 +290,6 @@@ config MOUSE_ELAN_I2C_SMBU
  
  	   If unsure, say Y.
  
- config MOUSE_INPORT
- 	tristate "InPort/MS/ATIXL busmouse"
- 	depends on ISA
- 	help
- 	  Say Y here if you have an InPort, Microsoft or ATI XL busmouse.
- 	  They are rather rare these days.
- 
- 	  To compile this driver as a module, choose M here: the
- 	  module will be called inport.
- 
- config MOUSE_ATIXL
- 	bool "ATI XL variant"
- 	depends on MOUSE_INPORT
- 	help
- 	  Say Y here if your mouse is of the ATI XL variety.
- 
- config MOUSE_LOGIBM
- 	tristate "Logitech busmouse"
 -config MOUSE_PC110PAD
 -	tristate "IBM PC110 touchpad"
--	depends on ISA
--	help
- 	  Say Y here if you have a Logitech busmouse.
- 	  They are rather rare these days.
 -	  Say Y if you have the IBM PC-110 micro-notebook and want its
 -	  touchpad supported.
--
--	  To compile this driver as a module, choose M here: the
- 	  module will be called logibm.
 -	  module will be called pc110pad.
--
  config MOUSE_AMIGA
  	tristate "Amiga mouse"
  	depends on AMIGA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-04-10 11:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=adjlNGglOUTLJ8hF@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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