mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Joe Perches <joe@perches.com>, Jaroslav Kysela <perex@perex.cz>,
	<alsa-devel@alsa-project.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] Improving or replacing snd_printk()
Date: Fri, 31 May 2013 16:34:08 +0200	[thread overview]
Message-ID: <s5hwqqf1an3.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1305311014330.1276-100000@iolanthe.rowland.org>

At Fri, 31 May 2013 10:24:51 -0400 (EDT),
Alan Stern wrote:
> 
> On Fri, 31 May 2013, Takashi Iwai wrote:
> 
> > > I don't see the complexity/hell in adding functions
> > > for specific types of struct * to reduce the complexity
> > > of the code though.  Centralizing those indirections
> > > into functions also generally reduces overall code size.
> > 
> > I don't mind to add the struct pointer to new snd_*() -- if we really
> > introduce them.  The bigger question is whether we really need to
> > introduce such, and if yes, what variants.  And for that, I don't
> > think we need to add many functions.  Maybe snd_card_<level>() would
> > be good.  But others don't seem to make sense to me (remember that I
> > suggest dropping CONFIG_SND_VERBOSE_PRINTK).
> 
> struct snd_card contains pointers to two different devices: dev and 
> card_dev.  Some contexts might want to use one of them for log messages 
> while other contexts might want to use the other.

Yes, there are some corner cases, indeed.

Also, another expected problem is that neither card->card_dev nor
card->dev are set when snd_card_err() is called.  Many drivers set the
device pointers at the late stage just before the device
registration.  So, systematic replacements won't work as expected in
many cases.  (The same is applied for replacement with dev_*(), too.)


Takashi

  reply	other threads:[~2013-05-31 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 19:27 Alan Stern
2013-05-29 19:51 ` Joe Perches
2013-05-30 18:14   ` Alan Stern
2013-05-30 18:49     ` [alsa-devel] " Jaroslav Kysela
2013-05-30 19:43       ` Alan Stern
2013-05-30 20:30         ` Joe Perches
2013-05-31  6:37       ` Takashi Iwai
2013-05-31  7:06         ` Joe Perches
2013-05-31  7:23           ` Takashi Iwai
2013-05-31  7:30             ` Joe Perches
2013-05-31  7:35               ` Takashi Iwai
2013-05-31  7:38                 ` Joe Perches
2013-05-31  7:58                   ` Takashi Iwai
2013-05-31 14:24                     ` Alan Stern
2013-05-31 14:34                       ` Takashi Iwai [this message]
2013-05-31 15:33                         ` Alan Stern
2013-05-31 15:38                           ` Takashi Iwai
2013-05-31 17:06                         ` Joe Perches

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=s5hwqqf1an3.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®