mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-input <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] input: mt updates for 2.6.38
Date: Thu, 9 Dec 2010 10:49:41 -0800	[thread overview]
Message-ID: <20101209184940.GB23781@core.coreip.homeip.net> (raw)
In-Reply-To: <4D011EA3.2000905@euromail.se>

On Thu, Dec 09, 2010 at 07:23:31PM +0100, Henrik Rydberg wrote:
> On 12/09/2010 09:58 AM, Dmitry Torokhov wrote:
> 
> > On Wed, Dec 08, 2010 at 10:02:52AM +0100, Henrik Rydberg wrote:
> >> Dmitry,
> >>
> >> Please pull from
> >>
> >>   git://git.kernel.org/pub/scm/linux/kernel/git/rydberg/input-mt.git next
> >>
> >> to receive input-mt updates for 2.6.38.
> >>
> >> The tree contains core changes as well as dependent changes to hid drivers. You
> >> also find the new hid-egalax driver in there, signed off by Jiri.
> > 
> > Pulled, thank you Henrik.
> > 
> > I wonder if we should move input-mt.h into input/mt.h (and if someone
> > would bother to input-polldev.h there that would be great too).
> 
> 
> Sure, I have been wondering about that too. Right away, or later?

Better sooner than later as you'll have less places to patch ;)

> 
> > Also I try to sync with mainline once per release, at -rc1, unless I
> > know that my changes will conflict with some other work. I'd recommend
> > you do the same so that when I pull from you I am getting just your
> > changes and not the rest of stuff from mainline.
> 
> 
> No problem - I will see what sync point you end up using, and I will rebase to
> the same point.

No, not rebase, pull please. Public branches should not be rebased, at
least not when they have been pulled from.

> 
> > BTW, we need to document dev->trkid to avoid complaints from 'make
> > htmldocs' and friends. I wonder if the patch below will do.
> 
> 
> Looks good, thanks.

OK. I take it as an acked-by then.

-- 
Dmitry

  reply	other threads:[~2010-12-09 19:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  9:02 Henrik Rydberg
2010-12-09  8:58 ` Dmitry Torokhov
2010-12-09  9:08   ` Dmitry Torokhov
2010-12-09 18:27     ` Henrik Rydberg
2010-12-09 18:48       ` Dmitry Torokhov
2010-12-09 19:11         ` Henrik Rydberg
2010-12-09 18:23   ` Henrik Rydberg
2010-12-09 18:49     ` Dmitry Torokhov [this message]
2010-12-09 19:10       ` Henrik Rydberg
2010-12-13  8:29 Henrik Rydberg
2010-12-13  9:13 ` Dmitry Torokhov
2010-12-16 11:37 Henrik Rydberg
2010-12-17 19:34 ` Dmitry Torokhov
2010-12-23 15:20 Henrik Rydberg
2010-12-28  1:42 ` 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=20101209184940.GB23781@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rydberg@euromail.se \
    /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

all inboxes | Powered by JetHome®