From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: linux-next: manual merge of the asm-generic tree with the input-current tree
Date: Wed, 4 Apr 2018 09:06:00 +1000 [thread overview]
Message-ID: <20180404090600.1ea10f79@canb.auug.org.au> (raw)
In-Reply-To: <20180315095656.6007fe3a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
Hi all,
On Thu, 15 Mar 2018 09:56:56 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> [Just adding Dimitry to cc]
>
> On Thu, 15 Mar 2018 09:37:05 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the asm-generic tree got a conflict in:
> >
> > drivers/input/joystick/analog.c
> >
> > between commit:
> >
> > c9ab800167e1 ("Input: analog - use get_cycles() on PPC")
> >
> > from the input-current tree and commits:
> >
> > 739d875dd698 ("mn10300: Remove the architecture")
> > 588020dcb92a ("treewide: simplify Kconfig dependencies for removed archs")
> >
> > from the asm-generic 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/input/joystick/analog.c
> > index a942c4ccd2af,eefac7978f93..000000000000
> > --- a/drivers/input/joystick/analog.c
> > +++ b/drivers/input/joystick/analog.c
> > @@@ -163,7 -163,7 +163,7 @@@ static unsigned int get_time_pit(void
> > #define GET_TIME(x) do { x = (unsigned int)rdtsc(); } while (0)
> > #define DELTA(x,y) ((y)-(x))
> > #define TIME_NAME "TSC"
> > - #elif defined(__alpha__) || defined(CONFIG_MN10300) || defined(CONFIG_ARM) || defined(CONFIG_ARM64) || defined(CONFIG_PPC) || defined(CONFIG_RISCV) || defined(CONFIG_TILE)
> > -#elif defined(__alpha__) || defined(CONFIG_ARM) || defined(CONFIG_ARM64) || defined(CONFIG_RISCV)
> > ++#elif defined(__alpha__) || defined(CONFIG_ARM) || defined(CONFIG_ARM64) || defined(CONFIG_PPC) || defined(CONFIG_RISCV)
> > #define GET_TIME(x) do { x = get_cycles(); } while (0)
> > #define DELTA(x,y) ((y)-(x))
> > #define TIME_NAME "get_cycles"
This conflict now exists between the input-current tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-04-03 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 22:37 linux-next: manual merge of the asm-generic tree with the input-current tree Stephen Rothwell
2018-03-14 22:56 ` Stephen Rothwell
2018-04-03 23:06 ` Stephen Rothwell [this message]
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=20180404090600.1ea10f79@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.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