From: Brandon Philips <bphilips@suse.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Adrian Bunk <bunk@kernel.org>,
Matthias Schwarzott <zzam@gentoo.org>,
v4l-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] no help text for DVB_TUNER_ITD1000
Date: Thu, 24 Apr 2008 14:08:21 -0700 [thread overview]
Message-ID: <20080424210821.GA14416@plankton> (raw)
In-Reply-To: <20080424172838.5df1da67@gaivota>
On 17:28 Thu 24 Apr 2008, Mauro Carvalho Chehab wrote:
> On Thu, 24 Apr 2008 23:22:57 +0300 Adrian Bunk <bunk@kernel.org> wrote:
> > The DVB_TUNER_ITD1000 option introduced by
> > commit 1881ee89e0fe03ac5bba9045acb3bea1818f9466
> > (V4L/DVB (7571): mt312: Cleanup buffer variables of read/write functions)
> > lacks a help text.
> >
> > Please add a help text.
>
> Thanks for pointing.
>
> I just noticed and prepared a patch. I should soon add it to devel branch
> at -git for people to review.
How is adding this Kconfig related to the patch that Matthias posted?
Once again, some very strange folding is happening as things are moving
into git.
http://article.gmane.org/gmane.linux.drivers.dvb/41017/match=mt312+cleanup+buffer+variables+read+write+functions
vs.
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=1881ee89e0fe03ac5bba9045acb3bea1818f9466;hp=dbad108bdcb30629c850f5606949510da010a686
Could I take a look at the scripts that are used to generate the git
tree? This is the second time in the last few weeks that something like
this has happened.
Cheers,
Brandon
next prev parent reply other threads:[~2008-04-24 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 20:22 no help text for DVB_TUNER_ITD1000 Adrian Bunk
2008-04-24 20:28 ` Mauro Carvalho Chehab
2008-04-24 21:08 ` Brandon Philips [this message]
2008-04-24 21:34 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2008-04-24 23:39 ` Mauro Carvalho Chehab
2008-04-25 0:23 ` Brandon Philips
2008-04-25 2:16 ` 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=20080424210821.GA14416@plankton \
--to=bphilips@suse.de \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=zzam@gentoo.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