public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>,
	Jonathan Santos <Jonathan.Santos@analog.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-iio@vger.kernel.org
Subject: Re: linux-next: manual merge of the iio tree with the spi tree
Date: Sun, 6 Jul 2025 11:50:53 +0100	[thread overview]
Message-ID: <20250706115053.368ce9e9@jic23-huawei> (raw)
In-Reply-To: <b0b0443d-143f-4e41-b8b8-91c6726e838f@baylibre.com>

On Thu, 3 Jul 2025 07:28:07 -0500
David Lechner <dlechner@baylibre.com> wrote:

> On 7/3/25 3:31 AM, Jonathan Cameron wrote:
> > On Thu, 3 Jul 2025 16:38:24 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >   
> >> Hi all,
> >>
> >> Today's linux-next merge of the iio tree got a conflict in:
> >>
> >>   MAINTAINERS
> >>
> >> between commit:
> >>
> >>   e47a324d6f07 ("dt-bindings: trigger-source: add ADI Util Sigma-Delta SPI")
> >>
> >> from the spi tree and commit:
> >>
> >>   0dd88eaa7126 ("dt-bindings: trigger-source: add generic GPIO trigger source")
> >>
> >> from the iio 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.
> >>  
> > Thanks Stephen,
> > 
> > David, do you prefer these merged or kept as separate entries?  
> 
> Ah, shoot, I forgot that we had added the gpio one and just made
> one section like this.
> 
> I think it would make sense to also merge the new adi one with
> the reset to keep things compact.
> 
Is there a path to do that cleanly given the multiple trees things are
coming from?  Maybe this is a let things resolve whatever way this cycle
and tidy up next?

> > 
> > I don't think it matters either way in practice though this is the
> > more complex merge (the other being just putting the blocks in order.
> > 
> > We can put a note in the pull request on preference but ultimately Linus
> > will resolve this however he prefers! 
> > 
> > Jonathan
> > 
> >   
> >> -- 
> >> Cheers,
> >> Stephen Rothwell
> >>
> >> diff --cc MAINTAINERS
> >> index dd764b947dab,d0809d62ff48..000000000000
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@@ -25333,19 -25201,15 +25341,20 @@@ TRADITIONAL CHINESE DOCUMENTATIO
> >>   M:	Hu Haowen <2023002089@link.tyut.edu.cn>
> >>   S:	Maintained
> >>   W:	https://github.com/srcres258/linux-doc
> >>  -T:	git git://github.com/srcres258/linux-doc.git doc-zh-tw
> >>  +T:	git https://github.com/srcres258/linux-doc.git doc-zh-tw
> >>   F:	Documentation/translations/zh_TW/
> >>   
> >> + TRIGGER SOURCE
> >> + M:	David Lechner <dlechner@baylibre.com>
> >> + S:	Maintained
> >> + F:	Documentation/devicetree/bindings/trigger-source/gpio-trigger.yaml
> >> + F:	Documentation/devicetree/bindings/trigger-source/pwm-trigger.yaml
> >> + 
> >>  +TRIGGER SOURCE - ADI UTIL SIGMA DELTA SPI
> >>  +M:	David Lechner <dlechner@baylibre.com>
> >>  +S:	Maintained
> >>  +F:	Documentation/devicetree/bindings/trigger-source/adi,util-sigma-delta-spi.yaml
> >>  +
> >> - TRIGGER SOURCE - PWM
> >> - M:	David Lechner <dlechner@baylibre.com>
> >> - S:	Maintained
> >> - F:	Documentation/devicetree/bindings/trigger-source/pwm-trigger.yaml
> >> - 
> >>   TRUSTED SECURITY MODULE (TSM) INFRASTRUCTURE
> >>   M:	Dan Williams <dan.j.williams@intel.com>
> >>   L:	linux-coco@lists.linux.dev  
> 
> 


  reply	other threads:[~2025-07-06 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  6:38 linux-next: manual merge of the iio tree with the spi tree Stephen Rothwell
2025-07-03  8:31 ` Jonathan Cameron
2025-07-03 12:28   ` David Lechner
2025-07-06 10:50     ` Jonathan Cameron [this message]
2025-07-06 16:15       ` David Lechner
2025-07-21  2:55         ` Stephen Rothwell
2025-07-24 13:49           ` Jonathan Cameron

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=20250706115053.368ce9e9@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Jonathan.Santos@analog.com \
    --cc=broonie@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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