From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 0/15] STAGING: add lirc device drivers
Date: Tue, 27 Jul 2010 16:33:32 -0300 [thread overview]
Message-ID: <4C4F348C.3040703@redhat.com> (raw)
In-Reply-To: <20100727182404.GE9465@redhat.com>
Em 27-07-2010 15:24, Jarod Wilson escreveu:
> On Tue, Jul 27, 2010 at 09:09:56AM -0700, Greg KH wrote:
>> On Tue, Jul 27, 2010 at 12:59:00PM -0300, Mauro Carvalho Chehab wrote:
>>> Em 26-07-2010 20:25, Jarod Wilson escreveu:
>>
>> Hm, Jarod, you forgot to cc: the staging maintainer, so I missed these
>> :)
>
> D'oh, sorry, yeah, realized that about 10 minutes after I sent everything.
> Figured I'd ping you if you hadn't said anything about 'em in a day or
> three.
>
>>> Greg,
>>>
>>> It is probably simpler to merge those files via my tree, as they depend
>>> on some changes scheduled for 2.6.36.
>>>
>>> Would it be ok for you if I merge them from my tree?
>>
>> No objection from me for them to go through your tree.
Ok, thanks. I'll merge the patches on my tree.
>>
>> Do you want me to handle the cleanup and other fixes after they go into
>> the tree, or do you want to also handle them as well (either is fine
>> with me.)
>
> Note that I've got a git tree I've been maintaining the lirc drivers in
> for a while, so whomever is ultimately the gateway, I can also stage
> cleanups there -- I'll certainly be pushing any cleanups I do on the lirc
> drivers there prior to sending along for upstream, or else I'm liable to
> lose track of them... :)
>
> http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-lirc.git
>
Well, maybe the easiest way would be if I handle the first merge, to be sure that
they'll reach linux-next and 2.6.36 at the right time, avoiding conflicts with some
core changes. After the merge, Jerod can handle it via his own tree.
Cheers,
Mauro
next prev parent reply other threads:[~2010-07-27 19:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 23:25 [PATCH 0/15] STAGING: add lirc device drivers Jarod Wilson
2010-07-26 23:26 ` [PATCH 01/15] staging/lirc: add lirc_bt829 driver Jarod Wilson
2010-07-26 23:27 ` [PATCH 02/15] staging/lirc: add lirc_ene0100 driver Jarod Wilson
2010-07-26 23:28 ` [PATCH 03/15] staging/lirc: add lirc_i2c driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 04/15] staging/lirc: add lirc_igorplugusb driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 05/15] staging/lirc: add lirc_imon driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 06/15] staging/lirc: add lirc_it87 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 07/15] staging/lirc: add lirc_ite8709 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 08/15] staging/lirc: add lirc_parallel driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 09/15] staging/lirc: add lirc_sasem driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 10/15] staging/lirc: add lirc_serial driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 11/15] staging/lirc: add lirc_sir driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 12/15] staging/lirc: add lirc_streamzap driver Jarod Wilson
2010-07-26 23:33 ` [PATCH 13/15] staging/lirc: add lirc_ttusbir driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 14/15] staging/lirc: add lirc_zilog driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 15/15] staging/lirc: wire up Kconfig and Makefile bits Jarod Wilson
2010-07-27 15:59 ` [PATCH 0/15] STAGING: add lirc device drivers Mauro Carvalho Chehab
2010-07-27 16:09 ` Greg KH
2010-07-27 18:24 ` Jarod Wilson
2010-07-27 19:33 ` Mauro Carvalho Chehab [this message]
2010-07-27 19:51 ` Greg KH
2010-07-28 2:17 ` Jarod Wilson
2010-07-27 18:17 ` Jarod Wilson
2010-07-27 19:24 ` Mauro Carvalho Chehab
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=4C4F348C.3040703@redhat.com \
--to=mchehab@redhat.com \
--cc=greg@kroah.com \
--cc=jarod@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).