[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2565257.LbcJLfl1sl@vostro.rjw.lan>
Date: Tue, 19 Jul 2016 04:41:52 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Octavian Purdila <octavian.purdila@...el.com>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: linux-next: manual merge of the pm tree with the i2c tree
On Sunday, July 17, 2016 08:14:48 PM Wolfram Sang wrote:
>
> > > > > > I fixed it up (I think, but it needs more work - see below) and can
> > > > >
> > > > > For a start, it generates this warning, now:
> > > > >
> > > > > drivers/i2c/i2c-core.c:269:20: warning: 'i2c_acpi_add_device' defined but not used [-Wunused-function]
> > > > > static acpi_status i2c_acpi_add_device(acpi_handle handle, u32 level,
> > > > > ^
> > > >
> > > > OK, thanks for the heads-up.
> > >
> > > Yes, thanks!
> > >
> > > >
> > > > Wolfram, what about if I exposed my "acpi-tables" branch for you to pull?
> > > >
> > > > You could resolve this in your tree then.
> > >
> > > I can pull it in, sure. For the fixup, I'd like a commitment from one of
> > > the ACPI experts (Jarkko, Mika, Andy), though. Otherwise I'd need to
> > > revert given that we are quite late in the cycle already.
> >
> > The branch is here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-tables
> >
> > The top-most commit is:
> >
> > fafe5306f201 ACPI: Rename configfs.c to acpi_configfs.c to prevent link error
> >
> > I won't rebase this branch going forward, so it is safe to pull.
> >
> > Please let me know how I can help with the conflict resolution.
>
> Well, not knowing much about ACPI, I just need the conflict resolution
> for my latest i2c/for-next and your above branch. If you want to do it,
> fine with me. But maybe Jarkko will be back to office on Monday, too.
Unfortunately, I don't see how these branches can be merged in a sensible
way without adding too much new code into the merge itself.
Something needs to be dropped and then rebased and applied again.
Thanks,
Rafael
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists