Linux Media Controller development
 help / color / mirror / Atom feed
From: Daniel Scheller <d.scheller.oss@gmail.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	linux-media@vger.kernel.org, mchehab@kernel.org,
	liplianin@netup.ru, rjkm@metzlerbros.de
Subject: Re: [PATCH] [media] ddbridge: use dev_* macros in favor of printk
Date: Wed, 21 Jun 2017 21:54:03 +0200	[thread overview]
Message-ID: <20170621215403.5035db43@audiostation.wuest.de> (raw)
In-Reply-To: <740f66fc-d256-489d-82e5-d8602dfaeaa2@iki.fi>

Am Wed, 21 Jun 2017 22:20:35 +0300
schrieb Antti Palosaari <crope@iki.fi>:

> On 06/21/2017 08:20 PM, Mauro Carvalho Chehab wrote:
> > Em Wed, 21 Jun 2017 19:14:40 +0200
> > Daniel Scheller <d.scheller.oss@gmail.com> escreveu:
> >   
> >> I intentionally left this in for the pr_info used in module_init_ddbridge(). If you prefer, we can ofc probably also leave this as printk like
> >>
> >> printk(KERN_INFO KBUILD_MODNAME ": Digital...");  
> > 
> > Ah, OK!  
> 
> But why you even need it? Probe should be first place you need to print 
> something and there is always proper device pointer.

This will be printed whenever the module is loaded. When in ddb_probe, you won't notice ever if the module is loaded for whatever reason if no DD card is there, or a card is present which isn't supported, and printed multiple times if you have more than one supported card (imagine a CTv6 plus module, and a CI Bridge, which gets common these days).

Let's keep it as it is, please.

Regards,
Daniel Scheller
-- 
https://github.com/herrnst

      reply	other threads:[~2017-06-21 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 16:53 [PATCH] [media] ddbridge: use dev_* macros in favor of printk Daniel Scheller
2017-06-21 17:08 ` Mauro Carvalho Chehab
2017-06-21 17:14   ` Daniel Scheller
2017-06-21 17:20     ` Mauro Carvalho Chehab
2017-06-21 19:20       ` Antti Palosaari
2017-06-21 19:54         ` Daniel Scheller [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=20170621215403.5035db43@audiostation.wuest.de \
    --to=d.scheller.oss@gmail.com \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=liplianin@netup.ru \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=rjkm@metzlerbros.de \
    /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