From: "Henrik Rydberg" <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: linux-next: manual merge of the input-mt tree with the input-current tree
Date: Thu, 5 Jul 2012 19:57:23 +0200 [thread overview]
Message-ID: <20120705175723.GA3286@polaris.bitmath.org> (raw)
In-Reply-To: <20120705171904.GA31383@core.coreip.homeip.net>
On Thu, Jul 05, 2012 at 10:19:05AM -0700, Dmitry Torokhov wrote:
> Hi Henrik,
>
> On Thu, Jul 05, 2012 at 11:57:14AM +0800, Daniel Kurtz wrote:
> > On Thu, Jul 5, 2012 at 11:52 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > Hi Henrik,
> > >
> > > Today's linux-next merge of the input-mt tree got a conflict in
> > > drivers/input/touchscreen/atmel_mxt_ts.c between commit 9b7e31bbf4bb
> > > ("Input: request threaded-only IRQs with IRQF_ONESHOT") from the
> > > input-current tree and commit c2ef9a1a248b ("Input: atmel_mxt_ts - use
> > > client name for irq") from the input-mt tree.
> > >
> > > I fixed it up (see below) and can carry the fix as necessary.
> >
> > Looks good to me. Don't know if you need it for a merge, but:
> >
> > Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
> >
>
> Hmm, maybe it is time I pull your tree?
By all means, I have nothing further planned for the merge window. I
wanted to wait until Linus pulls your current tree, then pull in the
merge conflict, then eventual reverts, then send you a pull
request. IOW, something like tomorrow. Sounds good?
Henrik
next prev parent reply other threads:[~2012-07-05 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 3:52 linux-next: manual merge of the input-mt tree with the input-current tree Stephen Rothwell
2012-07-05 3:57 ` Daniel Kurtz
2012-07-05 17:19 ` Dmitry Torokhov
2012-07-05 17:57 ` Henrik Rydberg [this message]
2012-07-06 5:25 ` Dmitry Torokhov
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=20120705175723.GA3286@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lars@metafoo.de \
--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