public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the iio tree with the char-misc.current tree
Date: Mon, 13 Jan 2025 06:19:50 +0100	[thread overview]
Message-ID: <2025011343-cannon-sprawl-f0e0@gregkh> (raw)
In-Reply-To: <20250113142342.4578868a@canb.auug.org.au>

On Mon, Jan 13, 2025 at 02:23:42PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 6 Jan 2025 15:21:07 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > Today's linux-next merge of the iio tree got a conflict in:
> > 
> >   drivers/iio/adc/ti-ads1119.c
> > 
> > between commit:
> > 
> >   54d394905c92 ("iio: adc: ti-ads1119: fix sample size in scan struct for triggered buffer")
> > 
> > from the char-misc.current tree and commit:
> > 
> >   2cfb4cd058d0 ("iio: adc: Use aligned_s64 instead of open coding alignment.")
> > 
> > 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.
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell
> > 
> > diff --cc drivers/iio/adc/ti-ads1119.c
> > index c268e27eec12,0a68ecdea4e6..000000000000
> > --- a/drivers/iio/adc/ti-ads1119.c
> > +++ b/drivers/iio/adc/ti-ads1119.c
> > @@@ -500,8 -500,8 +500,8 @@@ static irqreturn_t ads1119_trigger_hand
> >   	struct iio_dev *indio_dev = pf->indio_dev;
> >   	struct ads1119_state *st = iio_priv(indio_dev);
> >   	struct {
> >  -		unsigned int sample;
> >  +		s16 sample;
> > - 		s64 timestamp __aligned(8);
> > + 		aligned_s64 timestamp;
> >   	} scan;
> >   	unsigned int index;
> >   	int ret;
> 
> This is now a conflict between the char-misc tree and Linus' tree.
> 

Thanks, now resolved in my tree.

greg k-h

  reply	other threads:[~2025-01-13  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06  4:21 linux-next: manual merge of the iio tree with the char-misc.current tree Stephen Rothwell
2025-01-13  3:23 ` Stephen Rothwell
2025-01-13  5:19   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-29  4:35 Stephen Rothwell
2022-04-29  4:47 ` Stephen Rothwell
2022-05-01 18:09   ` Jonathan Cameron
2022-02-22 20:40 broonie

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=2025011343-cannon-sprawl-f0e0@gregkh \
    --to=greg@kroah.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=arnd@arndb.de \
    --cc=javier.carrasco.cruz@gmail.com \
    --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