mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Petar Stepanovic <pstepanovic@axiado.com>
Subject: linux-next: manual merge of the gpio-brgl tree with the iio tree
Date: Tue, 29 Sep 2026 15:57:02 +0100	[thread overview]
Message-ID: <arvRvrekUA3zEhYv@sirena.org.uk> (raw)

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

Hi all,

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

  MAINTAINERS

between commits:

  02f4bd272bf7b ("iio: adc: add Axiado SARADC driver")
  a84f9870c16ba ("dt-bindings: iio: adc: add Axiado AX3000/AX3005 SARADC")

from the iio tree and commits:

  a7787b818204d ("dt-bindings: gpio: add Axiado AX3005 SGPIO controller")
  dd36a4b7f391e ("gpio: axiado: add AX3005 SGPIO controller support")

from the gpio-brgl 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 MAINTAINERS
index b6400ebe7d2dd,9aea4c3fd3aee..0000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -4487,15 -4439,15 +4487,24 @@@ S:	Orpha
  F:	Documentation/devicetree/bindings/sound/axentia,*
  F:	sound/soc/atmel/tse850-pcm5142.c
  
 +AXIADO SARADC DRIVER
 +M:	Petar Stepanovic <pstepanovic@axiado.com>
 +M:	Akhila Kavi <akavi@axiado.com>
 +M:	Prasad Bolisetty <pbolisetty@axiado.com>
 +L:	linux-iio@vger.kernel.org
 +S:	Maintained
 +F:	Documentation/devicetree/bindings/iio/adc/axiado,ax3000-saradc.yaml
 +F:	drivers/iio/adc/axiado_saradc.c
 +
+ AXIADO SGPIO DRIVER
+ M:	Petar Stepanovic <pstepanovic@axiado.com>
+ M:	SriNavmani A <srinavmani@axiado.com>
+ M:	Prasad Bolisetty <pbolisetty@axiado.com>
+ L:	linux-gpio@vger.kernel.org
+ S:	Supported
+ F:	Documentation/devicetree/bindings/gpio/axiado,ax3005-sgpio.yaml
+ F:	drivers/gpio/gpio-axiado-sgpio.c
+ 
  AXIS ARTPEC ARM64 SoC SUPPORT
  M:	Jesper Nilsson <jesper.nilsson@axis.com>
  M:	Lars Persson <lars.persson@axis.com>

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

             reply	other threads:[~2026-09-29 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 14:57 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-17  3:56 Stephen Rothwell
2025-02-17  8:13 ` Bartosz Golaszewski

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=arvRvrekUA3zEhYv@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@bgdev.pl \
    --cc=jic23@kernel.org \
    --cc=jonathan.cameron@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pstepanovic@axiado.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

all inboxes | Powered by JetHome®