From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL] HVR-900 R2 and PCTV 330e DVB support
Date: Fri, 25 Mar 2011 13:45:05 -0300 [thread overview]
Message-ID: <4D8CC691.7020201@redhat.com> (raw)
In-Reply-To: <AANLkTimW+e8-YC=nFdiKYr=6TKYRozf8uAct21i5QHN0@mail.gmail.com>
Em 25-03-2011 13:09, Devin Heitmueller escreveu:
> On Fri, Mar 25, 2011 at 11:50 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> I've added a patch for it at the end of the series.
>>
>> Could you please double check if everything is ok, for me to move this upstream?
>>
>> Thanks!
>> Mauro
>>
>
> Sure, I will find some time this weekend to try out your tree.
Ok, thanks!
>
> http://git.linuxtv.org/mchehab/experimental.git?a=blobdiff;f=drivers/media/dvb/frontends/drxd.h;h=7113535844f2304f58e24571f538b9a71528cfb9;hp=d3d6c9246535def0e309f0714c9acbec0f350e25;hb=cf36b96eac59311f37b7881a6f48b465d1522fe9;hpb=df1bf4caabf1284289a4f6d7c1516e74c4e944c8
>
> This patch is a bit funny, because the latest version of Lindent
> actually introduced the space between "*" and "off". Might be
> something for you to consider looking at in the tool.
indent tool has some drawbacks. Sometimes, it does bad things, but when
the code has lots of issues, it is still better than nothing. Maybe it
believed that off is some keyword.
>
> Devin
>
next prev parent reply other threads:[~2011-03-25 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 17:05 [GIT PULL] HVR-900 R2 and PCTV 330e DVB support Devin Heitmueller
2011-03-24 17:34 ` Mauro Carvalho Chehab
2011-03-24 17:36 ` Devin Heitmueller
2011-03-25 15:50 ` Mauro Carvalho Chehab
[not found] ` <AANLkTimW+e8-YC=nFdiKYr=6TKYRozf8uAct21i5QHN0@mail.gmail.com>
2011-03-25 16:45 ` Mauro Carvalho Chehab [this message]
2011-04-02 10:43 ` Mauro Carvalho Chehab
2011-04-02 21:01 ` Devin Heitmueller
2011-04-02 22:47 ` 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=4D8CC691.7020201@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.com \
--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