From: Andy Walls <awalls@md.metrocast.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>, linux-media@vger.kernel.org
Subject: Re: [GIT PULL] More IR fixes for 2.6.38
Date: Wed, 26 Jan 2011 18:33:23 -0500 [thread overview]
Message-ID: <1296084803.2444.2.camel@localhost> (raw)
In-Reply-To: <4D405D8E.6020900@redhat.com>
On Wed, 2011-01-26 at 15:44 -0200, Mauro Carvalho Chehab wrote:
> Andy,
>
> Then, it is better to use Jarod's tree for it. His patches are against
> upstream, and are meant to be applied to .38. So, I need first to send
> them to linux-next, then to upstream and then merge from upstream,
> otherwise, I'll have to manually fix the conflicts on the next merge window.
> Due to LCA, I'm not sure if Linus will apply much patches during this
> week. So, I'll probably wait until next week to send Jarod's patches
> upstream.
> Jarod Wilson <jarod@redhat.com> wrote:
> >> git://linuxtv.org/jarod/linux-2.6-ir.git for-2.6.38
OK. I'll work off of Jarod's branch then.
Thanks.
Regards,
Andy
next prev parent reply other threads:[~2011-01-26 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 17:23 [GIT PULL] More IR fixes for 2.6.38 Andy Walls
2011-01-26 17:44 ` Mauro Carvalho Chehab
2011-01-26 23:33 ` Andy Walls [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-26 16:53 Jarod Wilson
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=1296084803.2444.2.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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