From: Andrey Utkin <andrey_utkin@fastmail.com>
To: Joe Perches <joe@perches.com>
Cc: "Andrey Utkin" <andrey.utkin@corp.bluecherry.net>,
"Mauro Carvalho Chehab" <mchehab@osg.samsung.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bluecherry Maintainers" <maintainers@bluecherrydvr.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Jiri Slaby" <jslaby@suse.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Guenter Roeck" <linux@roeck-us.net>,
"Kozlov Sergey" <serjk@netup.ru>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Hans Verkuil" <hans.verkuil@cisco.com>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, linux-pci@vger.kernel.org,
kernel-mentors@selenic.com
Subject: Re: [PATCH v4] [media] pci: Add tw5864 driver
Date: Wed, 13 Jul 2016 04:56:00 +0300 [thread overview]
Message-ID: <20160713015600.GG5934@zver> (raw)
In-Reply-To: <1468255253.8360.142.camel@perches.com>
On Mon, Jul 11, 2016 at 09:40:53AM -0700, Joe Perches wrote:
> Each of these blocks will start with the dev_<level> prefix
> and the subsequent lines will not have the same prefix
Yes. I have checked how it looks before submitting, but I didn't see
this as a problem. I don't mind changing that (anyway I have found few
micro-issues with checkpatch --strict and would like to resubmit), but
would like to hear some second opinion.
> It also might be better to issue something like a single
> line dev_warn referring to the driver code and just leave
> this comment in the driver sources.
>
> Something like:
>
> dev_warn(&pci_dev->dev,
> "This driver has known defects in video quality\n");
Things get complicated if you consider mainstream distros and their
years-behind kernels. The simplest way to preserve correspondence
between state of driver and such notice is to contain the notice in the
compiled driver. I hope the state of affairs will change to better
someday :)
next prev parent reply other threads:[~2016-07-13 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:17 [PATCH v4] [media] pci: Add tw5864 driver Andrey Utkin
2016-07-11 16:40 ` Joe Perches
2016-07-13 1:56 ` Andrey Utkin [this message]
2016-07-13 2:05 ` [PATCH v4] [media] pci: Add tw5864 driver - fixed few style nits, going to resubmit soon Andrey Utkin
2016-07-13 7:05 ` Hans Verkuil
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=20160713015600.GG5934@zver \
--to=andrey_utkin@fastmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.utkin@corp.bluecherry.net \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=kernel-mentors@selenic.com \
--cc=khalasa@piap.pl \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maintainers@bluecherrydvr.com \
--cc=mchehab@osg.samsung.com \
--cc=serjk@netup.ru \
/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).