From: hermann pitton <hermann-pitton@arcor.de>
To: BOUWSMA Barry <freebeer.bouwsma@gmail.com>
Cc: VDR User <user.vdr@gmail.com>,
"mailing list: linux-media" <linux-media@vger.kernel.org>,
Oliver Endriss <o.endriss@gmx.de>
Subject: Re: [PATCH] Fix av7110 driver name
Date: Sun, 13 Jun 2010 19:48:04 +0200 [thread overview]
Message-ID: <1276451284.3128.18.camel@pc07.localdom.local> (raw)
In-Reply-To: <alpine.DEB.2.01.1006131200580.17071@localhost.localdomain>
Hi Barry,
Am Sonntag, den 13.06.2010, 12:07 +0200 schrieb BOUWSMA Barry:
> On Sat (Saturday) 12.Jun (June) 2010, 05:10, VDR User wrote:
>
> > This patch simply changes the name of the av7110 driver to "AV7110"
> > instead of the generic "dvb" it's set to currently. Although it's
> > somewhat trivial, it still seems appropriate to fix the name to be
> > descriptive of the driver.
>
> Thanks Derek; I'll just note that as submitted, the trivial patch
> is a ``reversed'' patch, but I'd hope that any tools written for
> auto-patch-handing should be able to detect this and correct this
> issue.
>
> The other patch is in ``proper'' order, so no worries.
>
>
>
> > --- v4l-dvb/linux/drivers/media/dvb/ttpci/av7110.c 2010-06-11
> > 13:24:29.000000000 -0700
> > +++ v4l-dvb.orig/linux/drivers/media/dvb/ttpci/av7110.c 2010-06-11
> > 12:49:50.000000000 -0700
>
>
> > - .name = "AV7110",
> > + .name = "dvb",
>
>
> thanks,
> barry bouwsma
the whole situation, dealing with such sort of patches, also given the
noise for nothing previously, is of course somewhat unpleasant.
But out of such, we had best support from people not obviously related
to linux many times and that counts.
So, for my experience, it is always worth to have some rumble.
Cheers,
Hermann
prev parent reply other threads:[~2010-06-13 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 3:10 [PATCH] Fix av7110 driver name VDR User
2010-06-13 10:07 ` BOUWSMA Barry
2010-06-13 17:48 ` hermann pitton [this message]
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=1276451284.3128.18.camel@pc07.localdom.local \
--to=hermann-pitton@arcor.de \
--cc=freebeer.bouwsma@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=o.endriss@gmx.de \
--cc=user.vdr@gmail.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